[CVE-2026-53403][LOW] fbdev: Fix fb_new_modelist to prevent null-ptr-deref in fb_videomode_to_var

[CVE-2026-53403][LOW] fbdev: Fix fb_new_modelist to prevent null-ptr-deref in fb_videomode_to_var

[AL-KERNEL]

CVE: CVE-2026-53403
Priority: LOW
AL-KERNEL base severity: LOW
KPANIC flag: NO
Patch: fbdev: Fix fb_new_modelist to prevent null-ptr-deref in fb_videomode_to_var
Commit: 1458a4d804550b7101e8bb02c1cb941088e4c0c7
Upstream patch: https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git/commit/?id=1458a4d804550b7101e8bb02c1cb941088e4c0c7
Original CVE announcement: https://lore.kernel.org/linux-cve-announce/?q=CVE-2026-53403
Analysis date: Sun, 19 Jul 2026 11:09:18 -0400
ActionableScore: 1
ActionableScore lower bound: 0
Actionable bucket: Ordinary Moderate / Low-like
Manual review required: YES

Summary:
A local fbdev state-consistency bug can leave the current framebuffer mode absent from the modelist, causing a later fbcon takeover to dereference a NULL mode pointer and crash the kernel.

======================================================================
ABOUT THIS REPORT
======================================================================

The original Linux kernel CVE announcement for CVE-2026-53403 is available here:
https://lore.kernel.org/linux-cve-announce/?q=CVE-2026-53403

The original announcement does not normally provide a security severity
estimate, CVSS assessment, or enough information to determine whether the
reported kernel bug represents a practically relevant security issue.

This report was generated by AL-KERNEL, an AI-assisted Linux kernel
vulnerability analysis system developed by Alexander Larkin. It combines
an autonomous classifier with LLM-assisted technical analysis and a
separate ActionableScore mechanism.

The purpose of this report is to prioritize Linux kernel CVEs before
manual review, identify cases that require prompt investigation, and
support automatic closure of issues that are unlikely to have meaningful
security impact.

Published priority for this report: LOW
Manual review required: YES

A detailed explanation of the methodology and priority rules is included
at the end of this message.

======================================================================
AL-KERNEL CLASSIFICATION RESULT
======================================================================

CVE-2026-53403	LOW	CHECK WITH IMPACT FROM ORIG NN LOW	Maybe valid. Check manually. Hints by AL-KERNEL: The best (paranoid) CVSS is 'AV:L/AC:H/PR:L/UI:N/S:U/C:N/I:N/A:H';**CWE-476;CWE-754;*CWE-20;Other CVSS 'AV:L/AC:H/PR:H/UI:N/S:U/C:N/I:N/A:H';BEST CVSS score: '4.7';DESCR 'fbdev can hit a NULL pointer dereference when userspace replaces the framebuffer modelist with a list that does not contain the current info var mode. With fbcon unbound, no mapped console is repointed during fb_new_modelist, and a later console takeover can reach fb_videomode_to_var with a NULL mode pointer. For the CVSS the PR:L is used only in the paranoid score because some deployments may delegate framebuffer or console control to a reduced capability service or container root. The typical base case is PR:H because changing the modelist and fbcon binding is normally administrative. The issue is not network reachable and the impact is denial of service via kernel crash only.';NO MANUAL CHECK; ,and ActionableScore result is Ordinary Moderate / Low-like (with actual score 1)	YES	NULLPTR IMPROVEONLY LINUS  DECREASED_TO_MODERATE_REGULAR_FROM_MODERATE7_BASED_ON_GUESSCVSS_AND_CIANNH DECREASED_TO_LOW_FROM_MODERATE_BASED_ON_ACTIONABLESCORELESSTHAN3	NO	NO	checked

======================================================================
ACTIONABLESCORE ANALYSIS
======================================================================

ActionableScore=1
ActionableScoreLower=0

## 1. ActionableScore

* Conservative score: 0
* Paranoid score: 1
* Final recommended bucket: **Ordinary Moderate / Low-like**

## 2. Signal breakdown

* Reliable kernel crash / strong DoS: +1. The patch and commit describe a concrete NULL pointer dereference in `fb_videomode_to_var()` after `fb_display[i].mode` becomes NULL.
* Requires admin/root/CAP-like access in typical deployments: -2. Replacing framebuffer modelists and controlling fbcon binding/takeover is normally an administrative local operation.
* Special sequencing required: -1. The trigger requires replacing the modelist so it excludes `info->var`, having fbcon unbound or not mapped to the framebuffer, and later causing console takeover.
* Paranoid local reduced-privilege scenario: +1. If a product delegates framebuffer or console control to a reduced-capability service, container root, or local user group, the practical PR can be closer to PR:L than PR:H.
* No memory corruption bonus. This is a NULL pointer dereference, not UAF, OOB write, double free, type confusion, arbitrary write, or refcount/lifetime corruption.
* No confidentiality or integrity impact. The described failure path is crash-only.

Call-site confidence: high. The commit gives the relevant path: `store_modes()` -> `fb_new_modelist()` -> later console takeover -> `var_to_display()` -> `fbcon_switch()` -> `display_to_var()` -> `fb_videomode_to_var()`.

## 3. Reachability analysis

The bug is locally triggered through framebuffer/fbcon control paths. It is not network reachable. In normal deployments, access to framebuffer mode list modification and fbcon state changes is restricted to root or administrative services, so the conservative interpretation treats it as privileged local DoS. Namespaces and containers usually do not expose real host framebuffer control, but specialized appliances, kiosk systems, or delegated device-management services could reduce the practical privilege requirement.

## 4. Severity interpretation

This behaves like ordinary Moderate or Low-like kernel DoS, not Important. The theoretical impact is limited to a kernel crash from NULL pointer dereference. There is no evidence of attacker-controlled reclaim, stale object reuse, write-after-free, object confusion, or a data corruption primitive that would justify LPE concern. The issue should not be treated as actionable Moderate unless the evaluated product exposes fbdev/fbcon control to non-admin local users.

## 5. One-sentence report phrase

A local fbdev state-consistency bug can leave the current framebuffer mode absent from the modelist, causing a later fbcon takeover to dereference a NULL mode pointer and crash the kernel.

## 6. Manual review recommendation

NO MANUAL CHECK NEEDED.
NO MANUAL CHECK REQUIRED COULD BE AUTOCLOSED.

Reason: crash-only NULL pointer dereference, no remote reachability, no memory corruption primitive, and typical trigger requires administrative framebuffer or console control.

======================================================================
UPSTREAM PATCH SUMMARY
======================================================================

Patch: fbdev: Fix fb_new_modelist to prevent null-ptr-deref in fb_videomode_to_var
Commit: 1458a4d804550b7101e8bb02c1cb941088e4c0c7
Upstream URL: https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git/commit/?id=1458a4d804550b7101e8bb02c1cb941088e4c0c7

Commit description:

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.

Cc: stable@vger.kernel.org
Assisted-by: Claude:claude-opus-4-8
Signed-off-by: Ian Bridges <icb@fastmail.org>
Signed-off-by: Helge Deller <deller@gmx.de>
Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>

Changed files:
  drivers/video/fbdev/core/fbmem.c

Diff excerpt:

Not included in this email. See the upstream URL for the full patch.

Full patch:
https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git/commit/?id=1458a4d804550b7101e8bb02c1cb941088e4c0c7

======================================================================
DETAILED REPORT METHODOLOGY
======================================================================

The original Linux kernel CVE announcement for CVE-2026-53403 can be found here:
https://lore.kernel.org/linux-cve-announce/?q=CVE-2026-53403

The original CVE announcement normally does not include a security-level
estimate. In particular, it may not contain a CVSS assessment, an impact
level, or enough information to determine whether the reported bug is a
practically relevant security issue. One purpose of this parallel CVE list
is to provide that missing technical and prioritization information.

The original goal of the AL-KERNEL project was to prioritize Linux kernel
CVE analysis automatically before manual review. The system can also help
identify non-security issues that may be suitable for automatic closure.

This report was generated by AL-KERNEL, an AI-assisted Linux kernel
vulnerability analysis system developed by Alexander Larkin.

The first analysis stage combines an autonomous classifier with additional
LLM-based analysis. The autonomous classifier runs locally on a CPU and is
based on a backpropagation neural network. Together, these mechanisms
produce a technical vulnerability description, identify likely weakness
types, estimate CVSS severity, and provide input for ActionableScore.

Two CVSS estimates are retained because incomplete kernel vulnerability
information often permits more than one defensible interpretation:

  Conservative CVSS vector: AV:L/AC:H/PR:H/UI:N/S:U/C:N/I:N/A:H
  The Best / paranoid CVSS vector: AV:L/AC:H/PR:L/UI:N/S:U/C:N/I:N/A:H
  The Best / paranoid CVSS score: 4.7

The conservative vector represents a lower-impact interpretation.
The Best/paranoid vector intentionally represents a plausible upper-bound
interpretation and should not automatically be treated as demonstrated
real-world impact.

CVSS may also need to be adjusted for a particular Linux deployment,
because actual reachability, privileges, enabled kernel configuration,
hardware, namespaces, exposed device nodes, and other environmental
conditions can differ significantly between systems.

A separate ActionableScore mechanism evaluates practical remediation
urgency. Its analysis may include reachability, attack prerequisites,
subsystem exposure, memory-corruption characteristics, denial-of-service
reliability, and possible confidentiality, integrity, or
privilege-escalation impact.

  Conservative ActionableScore: 0
  Paranoid ActionableScore: 1

The final base severity is taken directly from the second tab-separated
field of the AL-KERNEL classification result. ActionableScore does not
replace or independently override that final AL-KERNEL decision, and
if ActionableScore adjusted impact level of ALKERNEL, then you would see
self-readable flags above like INCREASED_TO_HIGH_BASED_ON_ACTIONABLESCOREHIGHEREQTHAN7.

For an AL-KERNEL result of MODERATE, this report uses the following
additional presentation split:

  ActionableScore below 5   -> MODERATE REGULAR
  ActionableScore 5 or more -> MODERATE 7.0

The distinction between MODERATE REGULAR and MODERATE 7.0 makes it
possible to identify Moderate issues that should receive manual analysis
and fixes before lower-priority MODERATE REGULAR issues. In many cases,
MODERATE REGULAR fixes may wait for a later rebase or routine update.

There is one override in which MODERATE REGULAR becomes MODERATE 7.0
even when the ActionableScore is below 5. When the AL-KERNEL result
contains the KPANIC flag, a MODERATE result is always presented as
MODERATE 7.0. The KPANIC flag selected with few regexps without
usage of AI at all, so it helps to detect cases when Kernel Crash happens
and similar (to filter False-Negative results from the LLM usage).

KPANIC indicates that a reliable kernel crash, kernel panic, or similarly
serious kernel availability impact was identified by the classification
workflow.

AL-KERNEL base severity for this report: LOW
KPANIC detected for this report: NO
Published priority for this report (same as in Subject): LOW

These results are intended to support engineering triage. They are
machine-generated estimates, and cases marked for manual review should
be validated by a human security engineer before final disposition.
For more info read docs linked from here: https://kernelcve.org/
(and you can submit you own patch there to generate such a report
for non-existant CVE-id yet).

Note that in many cases this AI tool selects higher severity, than
real is (means you can expect Importants instead of Moderate 7.0 or
Moderates 7.0 instead of regular Moderates). If you see such cases,
please use reply email interface to add additional manual analyses
info to this particular CVE.
And please, please, let me know when you see Lows instead of Importants
or Important instead of Low (because particular for such cases I
need to tune this AI tool to make it better for this one and next similar).
My contact email for such notifications is alexanjelausa@gmail.com (and both
send reply to CVE record itself too and see "reply" button below for howto reply).