m68k: nfcon: Do not call console_is_registered() in nfcon_device() (CVE-2026-90158) | HOL Guard CVE

Unknown severity · Source severity not reportedCVE-2026-90158

m68k: nfcon: Do not call console_is_registered() in nfcon_device()

Answer in brief

CVE-2026-90158 records a Unknown severity vulnerability in m68k: nfcon: Do not call console_is_registered() in nfcon_device(). 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.

Published Sep 17, 2026Updated Sep 17, 2026Source checked Sep 17, 2026First seen by HOL Sep 17, 2026Material review Sep 17, 2026

Upstream Advisory

Key facts

Risk: Unknown severitySource severity not reported
Exploitation: Not marked as known exploited
Affected software: 2 mapped packages or products
Fix availability: Available

Why this deserves its current priority

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.

Affected scope and exposure questions

The current feed maps Linux/Linux (generic), Linux/Linux (generic). Check affected ranges and fixed versions before updating.

Mapped affected packages and fixed versions
Package	Affected range	Fixed version
Linux/Linuxgeneric	>=7c2af0f634f1bc761ca827310dc7e8e586af502f <7d3f15a664d115584fc177b5f2cfbdb3e5a50d60 \|\| >=7c2af0f634f1bc761ca827310dc7e8e586af502f <e5e11274b5512e24a346ed83f8dd85e3389d2f4b \|\| >=7c2af0f634f1bc761ca827310dc7e8e586af502f <be98f92fc244688a6bdecbc834cf2cd243056d9d \|\| >=7c2af0f634f1bc761ca827310dc7e8e586af502f <d73441232f1f067eb659e94447b1353c16609711 \|\| >=7c2af0f634f1bc761ca827310dc7e8e586af502f <2f8e3cad53b5c36ab0ed5d3195bfc55c59ea61a5	7d3f15a664d115584fc177b5f2cfbdb3e5a50d60, e5e11274b5512e24a346ed83f8dd85e3389d2f4b, be98f92fc244688a6bdecbc834cf2cd243056d9d, d73441232f1f067eb659e94447b1353c16609711, 2f8e3cad53b5c36ab0ed5d3195bfc55c59ea61a5
Linux/Linuxgeneric	6.2	Not reported

Recommended response

Check inventory. Check lockfiles and deployed manifests for Linux/Linux, Linux/Linux.
Review the reported fix. Update Linux/Linux to 7d3f15a664d115584fc177b5f2cfbdb3e5a50d60 if you use the affected versions. Test the change in a non-production environment first.

Evidence timeline and material changes

Published upstream
Sep 17, 2026
Evidence: source:cvelist:source_dates:source-dates:record
Source modified
Sep 17, 2026
Evidence: source:cvelist:source_dates:source-dates:record
First seen by HOL
Sep 17, 2026

Sources and claim methodology

Upstream source description

In the Linux kernel, the following vulnerability has been resolved: m68k: nfcon: Do not call console_is_registered() in nfcon_device() Since 7c2af0f634f1 ("tty: tty_io: use console_list_lock for list synchronization") show_cons_active() calls the .device() method under the console_list_lock, but console_is_registered() tries to acquire console_list_lock as well, causing a deadlock. It should not be necessary to check console_is_registered() here since the function should not be called in the fist place when the console is not registered.

Quoted source text, attributed separately from HOL analysis.