Answer in brief
CVE-2026-53403 records a Unknown severity vulnerability in fbdev: Fix fb_new_modelist to prevent null-ptr-deref in fb_videomode_to_var. 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-2026-53403 records a Unknown severity vulnerability in fbdev: Fix fb_new_modelist to prevent null-ptr-deref in fb_videomode_to_var. 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.
A CVSS score is not reported in the current record. 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.
| Package | Affected range | Fixed version |
|---|---|---|
| Linux/Linuxgeneric | >=1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 <1458a4d804550b7101e8bb02c1cb941088e4c0c7 || >=1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 <8707f02ac9f5f632039b60df2c9f3dc914709f72 || >=1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 <0d8c7f21ad8529d5c181e61f86be35b887ae2e4d || >=1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 <7640b4f68acb54c2c4f6b4a8aee0e9849dacd929 || >=1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 <4f1a7fe8ba845cb7d39580755f78c3b7b9a0b61e || >=1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 <eea16b6f805c0b1fb2f72f0f771088ea45356956 || >=1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 <88913059c77e171f44ba829282d42dde0d458811 || >=1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 <7f08fc10fa3d3366dc3af723970bd03d7d6d10e3 | 1458a4d804550b7101e8bb02c1cb941088e4c0c7, 8707f02ac9f5f632039b60df2c9f3dc914709f72, 0d8c7f21ad8529d5c181e61f86be35b887ae2e4d, 7640b4f68acb54c2c4f6b4a8aee0e9849dacd929, 4f1a7fe8ba845cb7d39580755f78c3b7b9a0b61e, eea16b6f805c0b1fb2f72f0f771088ea45356956, 88913059c77e171f44ba829282d42dde0d458811, 7f08fc10fa3d3366dc3af723970bd03d7d6d10e3 |
| Linux/Linuxgeneric | 2.6.12 | Not reported |
Published upstream
Jul 19, 2026
Evidence: source:cvelist:source_dates:source-dates:recordSource modified
Aug 17, 2026
Evidence: source:cvelist:source_dates:source-dates:recordFirst seen by HOL
Aug 17, 2026
In the Linux kernel, the following vulnerability has been resolved: fbdev: Fix fb_new_modelist to prevent null-ptr-deref in fb_videomode_to_var info->var, a framebuffer's current mode, is expected to have a matching entry in info->modelist. var_to_display() relies on this and treats a failed fb_match_mode() as "This should not happen". fb_set_var() keeps it true by adding the mode to the list on every change, and do_register_framebuffer() does the same at registration. store_modes() replaces the modelist from userspace. fb_new_modelist() validates the new modes but does not check that info->var still has a match. It relies on fbcon_new_modelist() to re-point consoles, but that only handles consoles mapped to the framebuffer. With fbcon unbound there are none, so info->var is left describing a mode that is no longer in the list. A later console takeover runs var_to_display(), where fb_match_mode() returns NULL and leaves fb_display[i].mode NULL. fbcon_switch() passes it to display_to_var(), and fb_videomode_to_var() dereferences the NULL mode. Keep the current mode in the list in fb_new_modelist(), the same way fb_set_var() does.
Quoted source text, attributed separately from HOL analysis.
A CVSS score is not reported in the current record. 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.
| Package | Affected range | Fixed version |
|---|---|---|
| Linux/Linuxgeneric | >=1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 <1458a4d804550b7101e8bb02c1cb941088e4c0c7 || >=1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 <8707f02ac9f5f632039b60df2c9f3dc914709f72 || >=1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 <0d8c7f21ad8529d5c181e61f86be35b887ae2e4d || >=1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 <7640b4f68acb54c2c4f6b4a8aee0e9849dacd929 || >=1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 <4f1a7fe8ba845cb7d39580755f78c3b7b9a0b61e || >=1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 <eea16b6f805c0b1fb2f72f0f771088ea45356956 || >=1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 <88913059c77e171f44ba829282d42dde0d458811 || >=1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 <7f08fc10fa3d3366dc3af723970bd03d7d6d10e3 | 1458a4d804550b7101e8bb02c1cb941088e4c0c7, 8707f02ac9f5f632039b60df2c9f3dc914709f72, 0d8c7f21ad8529d5c181e61f86be35b887ae2e4d, 7640b4f68acb54c2c4f6b4a8aee0e9849dacd929, 4f1a7fe8ba845cb7d39580755f78c3b7b9a0b61e, eea16b6f805c0b1fb2f72f0f771088ea45356956, 88913059c77e171f44ba829282d42dde0d458811, 7f08fc10fa3d3366dc3af723970bd03d7d6d10e3 |
| Linux/Linuxgeneric | 2.6.12 | Not reported |
Published upstream
Jul 19, 2026
Evidence: source:cvelist:source_dates:source-dates:recordSource modified
Aug 17, 2026
Evidence: source:cvelist:source_dates:source-dates:recordFirst seen by HOL
Aug 17, 2026
In the Linux kernel, the following vulnerability has been resolved: fbdev: Fix fb_new_modelist to prevent null-ptr-deref in fb_videomode_to_var info->var, a framebuffer's current mode, is expected to have a matching entry in info->modelist. var_to_display() relies on this and treats a failed fb_match_mode() as "This should not happen". fb_set_var() keeps it true by adding the mode to the list on every change, and do_register_framebuffer() does the same at registration. store_modes() replaces the modelist from userspace. fb_new_modelist() validates the new modes but does not check that info->var still has a match. It relies on fbcon_new_modelist() to re-point consoles, but that only handles consoles mapped to the framebuffer. With fbcon unbound there are none, so info->var is left describing a mode that is no longer in the list. A later console takeover runs var_to_display(), where fb_match_mode() returns NULL and leaves fb_display[i].mode NULL. fbcon_switch() passes it to display_to_var(), and fb_videomode_to_var() dereferences the NULL mode. Keep the current mode in the list in fb_new_modelist(), the same way fb_set_var() does.
Quoted source text, attributed separately from HOL analysis.