Skip to content
Noroxi
CVE-2026-72238· NVD / CVE Program· CNA Linux

x86/boot: Validate console=uart8250 baud rate to fix early boot hang

In the Linux kernel, the following vulnerability has been resolved: x86/boot: Validate console=uart8250 baud rate to fix early boot hang When the baud rate is empty, 0, invalid, or overflows to 0 when stored as an int, the system will hang during early boot because of a division by zero in early_serial_init(). Fall back to DEFAULT_BAUD when the resulting baud rate is 0 to prevent an early system hang.

—No exploit Fix available
Published
Aug 15, 2026
Updated
Aug 17, 2026
EPSS
0.2% · 11th percentile
CWE
—
Follow this CVE

Sign in to follow · You’ll be notified if a followed record enters KEV, gets an exploit or is updated.

Report tools

JSON

Action score

0

Monitor

Low priority for now.

CVSS
0 / 40 · —
CISA KEV
0 / 30 · Not listed
EPSS
0 / 30 · 0.2%

Noroxi analysis

No Noroxi analysis for this record yet

We don't hand-write analysis for the hundreds of thousands of vulnerabilities in the database; that wouldn't be honest. For notable, high-impact vulnerabilities our team writes the mechanism, detection and remediation steps.

We use this product, ask for help

Affected systems

—

Versions reported by the vendor

Affected version ranges reported by the assigning authority (Linux). Independent of NVD's CPE analysis and usually ahead of it.

  • Linux Linux

    • 2.6.36affected
    • ce0aa5dd20e44372f9617dd67c984f41fcdbed88 and later · before c1a276a731d02cbb728d0530f327a68728f2d8b0affected · git
    • ce0aa5dd20e44372f9617dd67c984f41fcdbed88 and later · before 24fbed0a2a45f5f379ef2b53bd2abe58be1142adaffected · git
    • ce0aa5dd20e44372f9617dd67c984f41fcdbed88 and later · before efa96a22613b86e05cd81229ce0be411c1a4a79aaffected · git
    • ce0aa5dd20e44372f9617dd67c984f41fcdbed88 and later · before 9a77a7639dfdc3eca417cd37620ce64da79c80c4affected · git
    • ce0aa5dd20e44372f9617dd67c984f41fcdbed88 and later · before b4d05032e9af7137eab8f3af2855073f896ca843affected · git
    • ce0aa5dd20e44372f9617dd67c984f41fcdbed88 and later · before f7c67c97b37c11f2a95c204092fb8159f2779e8faffected · git
    • ce0aa5dd20e44372f9617dd67c984f41fcdbed88 and later · before 4dad7e870c7e5178f71b5e1e4f67934b9e8cc207affected · git
    • ce0aa5dd20e44372f9617dd67c984f41fcdbed88 and later · before ffa0aa5b625fe0bed7463ac613f8b06676ff4542affected · git
    • before 2.6.36not affected · semver

Package-level exposure

OSV and GitHub Advisory data: ecosystem, package and range. SBOM matching uses this table.

EcosystemPackageAffected rangeFix
Debian:12linuxbefore 6.1.180-16.1.180-1
Debian:13linuxbefore 6.12.100-16.12.100-1
Debian:14linuxbefore 7.1.5-17.1.5-1

Same product

linux: all records

Other highest-scoring records for the same primary product.

  • CVE-2026-74705udp: fix potential use-after-free in tunnel segmentation
    40Plan
  • CVE-2026-74612veth: fix skb length accounting after XDP frag adjustment
    40Plan
  • CVE-2026-74475vxlan: use neigh_ha_snapshot() in route_shortcircuit()
    40Plan
  • CVE-2026-74309vdpa/octeon_ep: fix IRQ-to-ring mapping in interrupt handler
    40Plan
  • CVE-2026-74280crypto: marvell/octeontx - fix DMA cleanup using wrong loop index
    40Plan
  • CVE-2026-74279crypto: cavium/cpt - fix DMA cleanup using wrong loop index
    40Plan

Remediation

Which version to upgrade to

Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.

Product / packageFixed versionSource
Linux Linux24fbed0a2a45f5f379ef2b53bd2abe58be1142adVendor (CNA)
Linux Linux4dad7e870c7e5178f71b5e1e4f67934b9e8cc207Vendor (CNA)
Linux Linux9a77a7639dfdc3eca417cd37620ce64da79c80c4Vendor (CNA)
Linux Linuxb4d05032e9af7137eab8f3af2855073f896ca843Vendor (CNA)
Linux Linuxc1a276a731d02cbb728d0530f327a68728f2d8b0Vendor (CNA)
Linux Linuxefa96a22613b86e05cd81229ce0be411c1a4a79aVendor (CNA)
Linux Linuxf7c67c97b37c11f2a95c204092fb8159f2779e8fVendor (CNA)
Linux Linuxffa0aa5b625fe0bed7463ac613f8b06676ff4542Vendor (CNA)
debian:linux6.1.180-1 · Debian:12Package registry (OSV)

Exploit status

No known public exploit

No public exploit has been observed yet. That doesn't mean you're safe, only that the bar is a little higher.

Research context

For pentesters and researchers: attack profile, score disagreement, timeline, patch commits, credits, variant and chain candidates, bug bounty scope. All derived from existing data; no exploit code.

Timeline

From publication to today: proof of concept, Metasploit module, CISA KEV and fix record. Dates are as reported by the sources.

No dated events beyond publication.

EPSS, last 120 days

FIRST EPSS daily score; only changes of 0.01 or more are recorded (step chart).

Patch and commit links

Commit, PR and diff links among the references. A starting point for patch-diffing and variant hunting; fixes, not exploits.

No commit or PR link among the references.

Credits

All researchers

Finders, reporters and analysts named in the CNA record. Click a name for that researcher’s other records.

No credits in the CNA record.

Variant candidates

Same product, same weakness class, within 18 months. If the patch missed the root cause, the sibling bug is here.

No nightly-computed relations.

Chain candidates

An authentication bypass and a privilege-requiring bug in the same product, published close together: combined they may become an unauthenticated path.

—

Bug bounty scope

No known public program.

Source: bounty-targets-data (public HackerOne, Bugcrowd, Intigriti, YesWeHack listings).

Technical details

No CVSS vector for this record, so attack conditions can't be derived.

Weakness class (CWE)

—

Attack context

MITRE CAPEC attack patterns and ATT&CK techniques for this weakness class (CWE). A starting point for detection rules and threat hunting.

MITRE has no CAPEC/ATT&CK mapping for this CWE.

Change log

  1. Fix✗ → ✓

For records you follow, these changes also arrive as notifications. →

References

Vendor advisories and official records. Exploit/PoC links are deliberately left out.

All records