Skip to main content
VulnerabilityPublished Updated

CVE-2026-43197: Linux kernel · netconsole: avoid OOB reads, msg is not nul-terminated

Affects Linux kernelSource CVE Database V5

0

Not known to be exploited · CVSS 9.1 Critical · fixed in 3126a2f98beaec5a554a1fb31c46db1e8542665e : patch Linux kernel as a priority.

Data as of 26 Oct 2026, 12:55 UTC

CVSS 3.1 base score
9.1Critical
How severe the flaw is on the 0–10 CVSS scale.
EPSS
0.5% chance of exploitation in 30 days – higher than 47% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
CISA SSVC
Exploitation
No evidence of active exploitation and no public proof of concept
Automatable
Attackers can reliably automate steps 1–4 of the kill chain
Technical impact
Limited control over the software or limited information exposure

CISA SSVC assessment, 2026-10-16.

Patch
Available – fixed in 3126a2f98beaec5a554a1fb31c46db1e8542665e, 82aec772fca2223bc5774bd9af486fd95766e578, 74ab1456eaa3b2eb986138f9e1f4cb37e73b6f58 +2
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:H

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 6 May 2026

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponised: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq Mirage: no evidence on record.

    No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 26 Oct 2026.

What to do

Upgrade to a fixed release listed under Affected software.

Affected software

ProductAffectedFixed in
LinuxLinuxAffected
  • ≥ c62c0a17f9b7398022f9eebe547878033264f81f, < 3126a2f98beaec5a554a1fb31c46db1e8542665e
Fixed in
  • 3126a2f98beaec5a554a1fb31c46db1e8542665e
LinuxLinuxAffected
  • ≥ c62c0a17f9b7398022f9eebe547878033264f81f, < 82aec772fca2223bc5774bd9af486fd95766e578
Fixed in
  • 82aec772fca2223bc5774bd9af486fd95766e578
LinuxLinuxAffected
  • ≥ c62c0a17f9b7398022f9eebe547878033264f81f, < 74ab1456eaa3b2eb986138f9e1f4cb37e73b6f58
Fixed in
  • 74ab1456eaa3b2eb986138f9e1f4cb37e73b6f58
LinuxLinuxAffected
  • ≥ c62c0a17f9b7398022f9eebe547878033264f81f, < 68fe91df6ea822dae772fceaad0686e4f5839aec
Fixed in
  • 68fe91df6ea822dae772fceaad0686e4f5839aec
LinuxLinuxAffected
  • ≥ c62c0a17f9b7398022f9eebe547878033264f81f, < 8fe132c4873f9eb1b86ddbf31216e9d961a0b8b9
Fixed in
  • 8fe132c4873f9eb1b86ddbf31216e9d961a0b8b9
LinuxLinuxAffected
  • =6.6
Fixed in–

Description

In the Linux kernel, the following vulnerability has been resolved: netconsole: avoid OOB reads, msg is not nul-terminated msg passed to netconsole from the console subsystem is not guaranteed to be nul-terminated. Before recent commit 7eab73b18630 ("netconsole: convert to NBCON console infrastructure") the message would be placed in printk_shared_pbufs, a static global buffer, so KASAN had harder time catching OOB accesses. Now we see: printk: console [netcon_ext0] enabled BUG: KASAN: slab-out-of-bounds in string+0x1f7/0x240 Read of size 1 at addr ffff88813b6d4c00 by task pr/netcon_ext0/594 CPU: 65 UID: 0 PID: 594 Comm: pr/netcon_ext0 Not tainted 6.19.0-11754-g4246fd6547c9 Call Trace: kasan_report+0xe4/0x120 string+0x1f7/0x240 vsnprintf+0x655/0xba0 scnprintf+0xba/0x120 netconsole_write+0x3fe/0xa10 nbcon_emit_next_record+0x46e/0x860 nbcon_kthread_func+0x623/0x750 Allocated by task 1: nbcon_alloc+0x1ea/0x450 register_console+0x26b/0xe10 init_netconsole+0xbb0/0xda0 The buggy address belongs to the object at ffff88813b6d4000 which belongs to the cache kmalloc-4k of size 4096 The buggy address is located 0 bytes to the right of allocated 3072-byte region [ffff88813b6d4000, ffff88813b6d4c00)

References

Community reviews

Loading reviews…