Skip to content
Noroxi
NVD / CVE Program· CNA Linux

CVE-2026-63949: auxdisplay: line-display: fix OOB read on zero-length message_store()

HighCVSS 7.1 · v3.1—No exploit Fix available

Noroxi assessment

Priority: Monitor (action score 28/100)

  • The sources we track (CISA KEV, Exploit-DB, Metasploit, Nuclei, GitHub) show no public exploit code or exploitation in the wild.
  • Probability of exploitation in the next 30 days: 0.12% (FIRST EPSS).
  • Someone with local access to the system can trigger it. A low-privileged account is enough. No user action is required. No special conditions are required; it is repeatable.
  • Fixed version: Linux Linux 197476b126010bac1b3199833c6966cd6f54c2a9, 3859960daeb9b7b39b9847b5b0113bc6081eb735, 6ad4f75ef9f3372fce8cad494e789ac6a5507bef.

Low priority for now. Upgrade to Linux Linux 197476b126010bac1b3199833c6966cd6f54c2a9, 3859960daeb9b7b39b9847b5b0113bc6081eb735, 6ad4f75ef9f3372fce8cad494e789ac6a5507bef or later.

Generated automatically from the record's data: CVSS (NVD and CNA), CISA KEV and SSVC, FIRST EPSS, exploit sources, fixed versions. How we calculate it

Primary sources: NVD · CVE.org · FIRST EPSS

In the Linux kernel, the following vulnerability has been resolved: auxdisplay: line-display: fix OOB read on zero-length message_store() linedisp_display() unconditionally reads msg[count - 1] before checking whether count is zero, so a write of zero bytes to the message sysfs attribute hits msg[-1]: write(fd, "", 0); -> message_store(..., buf, count=0) -> linedisp_display(linedisp, buf, count=0) -> msg[count - 1] == '\n' ; OOB read The kernfs write buffer for that store is a 1-byte allocation (kernfs_fop_write_iter() does kmalloc(len + 1) with len == 0), so msg[-1] is a 1-byte read before the slab object. On a KASAN-enabled kernel this trips an out-of-bounds report and panics; on stock kernels it silently reads adjacent slab data and, if that byte happens to be '\n', the following count-- wraps ssize_t 0 to -1 and is then passed to kmemdup_nul(). linedisp_display() is reached from the message_store() sysfs callback (drivers/auxdisplay/line-display.c message attribute, mode 0644) and from the in-tree initial-message setup with count == -1, so the OOB path is only userspace-triggerable via zero-byte writes; vfs_write() does not short-circuit on count == 0 and kernfs_fop_write_iter() dispatches the store callback regardless. Guard the trailing-newline trim with a count check. The existing if (!count) block then takes the clear-display path unchanged. Affects every auxdisplay driver that registers via linedisp_register() / linedisp_attach(): ht16k33, max6959, img-ascii-lcd, seg-led-gpio.

Published
Jul 19, 2026
Updated
Oct 30, 2026
EPSS
0.1% · 2th percentile

Report tools

JSON

Action score

28

Monitor

Low priority for now.

CVSS
28 / 40 · 7.1 / 10
CISA KEV
0 / 30 · Not listed
EPSS
0 / 30 · 0.1%

Get told when this record changes

  • Not in KEV: no record of exploitation in the wild
  • No public exploit code on record
  • A fix has been released

If any of these changes, we'll tell you in the daily email digest.

Follow CVE-2026-63949

When you'll hear from us

  • when it enters CISA KEV
  • when exploit code appears or is weaponized
  • when the record is updated (including a fixed version)
  • when EPSS rises 20 points in a week

One daily email digest (06:00 UTC); connect a webhook for KEV listings and weaponized exploits every 10 minutes on paid plans, on the hour on the free plan.

Your free account also gets you

  • CVE alerts: add the products and versions you run, get the new CVEs that affect them
  • Uptime monitoring: 1 site, instant email when it goes down
  • Add your domain: subdomains and takeover risk scanned every week (1 domain)
  • 10 scans an hour on the security tools, at most 30 a day (3 a day without an account), an API key and MCP
  • All your scans in one panel: findings, what changed in the last scan, a report per domain or per client (PDF, share link)
All free tools
Is your version affected? Check it

Noroxi analysis

What does it mean in your environment?

The assessment above is generated automatically from the record's data; it doesn't know your environment. Our team verifies on your systems whether this vulnerability is actually exploitable and which mitigation is enough.

We use this product, ask for help

Affected systems

Is your version affected?

Pick the product and type the version you run. It's compared with this record's version ranges in your browser; the version isn't sent anywhere.

VendorProduct
linuxlinux kernel

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

    • 5.16affected
    • 7e76aece6f036cb7ada4858d6aa73825bfe22983 and later · before ca5b0781946d5083ceafa752141f47f085853620affected · git
    • 7e76aece6f036cb7ada4858d6aa73825bfe22983 and later · before 8776032fe989a9b5fc77f2de5e03e4adb44c630eaffected · git
    • 7e76aece6f036cb7ada4858d6aa73825bfe22983 and later · before 3859960daeb9b7b39b9847b5b0113bc6081eb735affected · git
    • 7e76aece6f036cb7ada4858d6aa73825bfe22983 and later · before 197476b126010bac1b3199833c6966cd6f54c2a9affected · git
    • 7e76aece6f036cb7ada4858d6aa73825bfe22983 and later · before 6ad4f75ef9f3372fce8cad494e789ac6a5507befaffected · git
    • 7e76aece6f036cb7ada4858d6aa73825bfe22983 and later · before a7511dcd9dd4bc55d123f9b800c8a4ed2662e5c6affected · git
    • before 5.16not affected · semver
    • 6.1.176 and later · up to and including 6.1.*not affected · semver
    • 6.6.143 and later · up to and including 6.6.*not 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.176-16.1.176-1
Debian:13linuxbefore 6.12.94-16.12.94-1
Debian:14linuxbefore 7.0.12-17.0.12-1

Other highest-scoring records for the same primary product.

  • CVE-2026-31431crypto: algif_aead - Revert to operating out-of-placeKEV
    90Now
  • CVE-2022-0847A flaw was found in the way the "flags" member of the new pipe buffer structure was lacking proper initialization in copy_page_to_iter_pipe…KEV
    89Now
  • CVE-2021-22555Heap Out-Of-Bounds Write in Netfilter IP6T_SO_SET_REPLACEKEV
    85Now

Published before and after this one in the same product

  • ← EarlierCVE-2026-63947Jul 19, 2026 · Bluetooth: HIDP: fix missing length checks in hidp_input_report()
    35Monitor
  • ← EarlierCVE-2026-63948Jul 19, 2026 · Bluetooth: L2CAP: fix chan ref leak in l2cap_chan_timeout() on !conn
    22Monitor
  • Later →CVE-2026-63950Jul 19, 2026 · mm/rmap: initialize nr_pages to 1 at loop start in try_to_unmap_one
    31Monitor

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 Linux197476b126010bac1b3199833c6966cd6f54c2a9Vendor (CNA)
Linux Linux3859960daeb9b7b39b9847b5b0113bc6081eb735Vendor (CNA)
Linux Linux6ad4f75ef9f3372fce8cad494e789ac6a5507befVendor (CNA)
Linux Linux8776032fe989a9b5fc77f2de5e03e4adb44c630eVendor (CNA)
Linux Linuxa7511dcd9dd4bc55d123f9b800c8a4ed2662e5c6Vendor (CNA)
Linux Linuxca5b0781946d5083ceafa752141f47f085853620Vendor (CNA)
debian:linux6.1.176-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).

Not on record for this CVE: patch commit or PR link · researcher credit · variant or chain candidate · public bounty program.

Technical details

Attack conditions

  • Someone with local access to the system can trigger it.
  • A low-privileged account is enough.
  • No user action is required.
  • No special conditions are required; it is repeatable.

If successful

Confidentiality
high · data can be read
Integrity
none
Availability
high · the service can be disrupted
Attack vector
Local
Attack complexity
Low
Privileges required
Low
User interaction
None
Scope
Unchanged
Confidentiality impact
High
Integrity impact
None
Availability impact
High

Weakness class (CWE)

CWE-125 · Out-of-bounds Read

CVSS vector

CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:H

nvd-primary

Attack context

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

ATT&CK techniques

—

Change log

  1. CVSS— → 7.1
  2. Severity— → high
  3. Fix✗ → ✓

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

References

All records