Answer in brief
CVE-2021-47383 records a High severity (CVSS 7.8) vulnerability in tty: Fix out-of-bound vmalloc access in imageblit. The current sources do not mark it as known exploited. The current feed maps Linux/Linux (generic), Linux/Linux (generic). Check affected ranges and fixed versions before updating.
Analysis pending evidence review
HOL Guard separates source facts from reviewed analysis. See the methodology.
Answer in brief
CVE-2021-47383 records a High severity (CVSS 7.8) vulnerability in tty: Fix out-of-bound vmalloc access in imageblit. The current sources do not mark it as known exploited. The current feed maps Linux/Linux (generic), Linux/Linux (generic). Check affected ranges and fixed versions before updating.
Analysis pending evidence review
HOL Guard separates source facts from reviewed analysis. See the methodology.
CVSS is 7.8. The current sources do not mark it as known exploited. Treat this as a source-backed prioritization signal, not a statement about your environment.
Analysis status
Analysis pending evidence review
Factual feed record only; HOL analysis is not approved for indexing. Read the methodology.
The current feed maps Linux/Linux (generic), Linux/Linux (generic). Check affected ranges and fixed versions before updating.
| Product | Affected versions | Fixed versions |
|---|---|---|
| cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:* | Not reported | Not reported |
| Package | Affected range | Fixed version |
|---|---|---|
| Linux/Linuxgeneric | 2.6.12 | Not reported |
| Linux/Linuxgeneric | >=1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 <7e71fcedfda6f7de18f850a6b36e78d78b04476f || >=1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 <70aed03b1d5a5df974f456cdc8eedb213c94bb8b || >=1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 <067c694d06040db6f0c65281bb358452ca6d85b9 || >=1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 <8a6a240f52e14356386030d8958ae8b1761d2325 || >=1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 <883f7897a25e3ce14a7f274ca4c73f49ac84002a || >=1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 <d570c48dd37dbe8fc6875d4461d01a9554ae2560 || >=1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 <699d926585daa6ec44be556cdc1ab89e5d54557b || >=1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 <3b0c406124719b625b1aba431659f5cdc24a982c | 7e71fcedfda6f7de18f850a6b36e78d78b04476f, 70aed03b1d5a5df974f456cdc8eedb213c94bb8b, 067c694d06040db6f0c65281bb358452ca6d85b9, 8a6a240f52e14356386030d8958ae8b1761d2325, 883f7897a25e3ce14a7f274ca4c73f49ac84002a, d570c48dd37dbe8fc6875d4461d01a9554ae2560, 699d926585daa6ec44be556cdc1ab89e5d54557b, 3b0c406124719b625b1aba431659f5cdc24a982c |
Published upstream
May 21, 2024
Evidence: source:cvelist:source_dates:source-dates:recordSource modified
Aug 5, 2026
Evidence: source:cvelist:source_dates:source-dates:recordFirst seen by HOL
Aug 4, 2026
In the Linux kernel, the following vulnerability has been resolved: tty: Fix out-of-bound vmalloc access in imageblit This issue happens when a userspace program does an ioctl FBIOPUT_VSCREENINFO passing the fb_var_screeninfo struct containing only the fields xres, yres, and bits_per_pixel with values. If this struct is the same as the previous ioctl, the vc_resize() detects it and doesn't call the resize_screen(), leaving the fb_var_screeninfo incomplete. And this leads to the updatescrollmode() calculates a wrong value to fbcon_display->vrows, which makes the real_y() return a wrong value of y, and that value, eventually, causes the imageblit to access an out-of-bound address value. To solve this issue I made the resize_screen() be called even if the screen does not need any resizing, so it will "fix and fill" the fb_var_screeninfo independently.
Quoted source text, attributed separately from HOL analysis.
CVSS is 7.8. The current sources do not mark it as known exploited. Treat this as a source-backed prioritization signal, not a statement about your environment.
Analysis status
Analysis pending evidence review
Factual feed record only; HOL analysis is not approved for indexing. Read the methodology.
The current feed maps Linux/Linux (generic), Linux/Linux (generic). Check affected ranges and fixed versions before updating.
| Product | Affected versions | Fixed versions |
|---|---|---|
| cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:* | Not reported | Not reported |
| Package | Affected range | Fixed version |
|---|---|---|
| Linux/Linuxgeneric | 2.6.12 | Not reported |
| Linux/Linuxgeneric | >=1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 <7e71fcedfda6f7de18f850a6b36e78d78b04476f || >=1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 <70aed03b1d5a5df974f456cdc8eedb213c94bb8b || >=1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 <067c694d06040db6f0c65281bb358452ca6d85b9 || >=1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 <8a6a240f52e14356386030d8958ae8b1761d2325 || >=1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 <883f7897a25e3ce14a7f274ca4c73f49ac84002a || >=1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 <d570c48dd37dbe8fc6875d4461d01a9554ae2560 || >=1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 <699d926585daa6ec44be556cdc1ab89e5d54557b || >=1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 <3b0c406124719b625b1aba431659f5cdc24a982c | 7e71fcedfda6f7de18f850a6b36e78d78b04476f, 70aed03b1d5a5df974f456cdc8eedb213c94bb8b, 067c694d06040db6f0c65281bb358452ca6d85b9, 8a6a240f52e14356386030d8958ae8b1761d2325, 883f7897a25e3ce14a7f274ca4c73f49ac84002a, d570c48dd37dbe8fc6875d4461d01a9554ae2560, 699d926585daa6ec44be556cdc1ab89e5d54557b, 3b0c406124719b625b1aba431659f5cdc24a982c |
Published upstream
May 21, 2024
Evidence: source:cvelist:source_dates:source-dates:recordSource modified
Aug 5, 2026
Evidence: source:cvelist:source_dates:source-dates:recordFirst seen by HOL
Aug 4, 2026
In the Linux kernel, the following vulnerability has been resolved: tty: Fix out-of-bound vmalloc access in imageblit This issue happens when a userspace program does an ioctl FBIOPUT_VSCREENINFO passing the fb_var_screeninfo struct containing only the fields xres, yres, and bits_per_pixel with values. If this struct is the same as the previous ioctl, the vc_resize() detects it and doesn't call the resize_screen(), leaving the fb_var_screeninfo incomplete. And this leads to the updatescrollmode() calculates a wrong value to fbcon_display->vrows, which makes the real_y() return a wrong value of y, and that value, eventually, causes the imageblit to access an out-of-bound address value. To solve this issue I made the resize_screen() be called even if the screen does not need any resizing, so it will "fix and fill" the fb_var_screeninfo independently.
Quoted source text, attributed separately from HOL analysis.