Bug 2577761 (CVE-2026-99785) - CVE-2026-99785 kernel: kernel: Out-of-bounds write via oversized 9p virtio mount tag
Summary: CVE-2026-99785 kernel: kernel: Out-of-bounds write via oversized 9p virtio mo...
Keywords:
Status: NEW
Alias: CVE-2026-99785
Product: Security Response
Classification: Other
Component: vulnerability
Version: unspecified
Hardware: All
OS: Linux
high
high
Target Milestone: ---
Assignee: Product Security DevOps Team
QA Contact:
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2026-11-20 06:12 UTC by OSIDB Bzimport
Modified: 2026-11-20 10:56 UTC (History)
17 users (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed:
Embargoed:


Attachments (Terms of Use)

Description OSIDB Bzimport 2026-11-20 06:12:26 UTC
In the Linux kernel, the following vulnerability has been resolved:

9p/trans_virtio: reject mount tags longer than NAME_MAX at probe

p9_virtio_probe() reads a 16-bit mount tag length (tag_len) from the
device config and kzalloc()s tag_len + 1 bytes for chan->tag with no
upper bound. A malicious or compromised host can present a tag of up to
65535 bytes; that tag is later copied into the single-page sysfs buffer
by p9_mount_tag_show() (memcpy(buf, chan->tag, tag_len + 1)), a
host-controlled out-of-bounds write of up to ~64 KiB past the PAGE_SIZE
attribute buffer.

Reject an overlong tag at probe time. A 9p mount tag is a name-like
identifier, so bound it by NAME_MAX (255): that limit is independent of
the sysfs/seq_file page size and is far above any legitimate mount tag,
which keeps p9_mount_tag_show() safe at the root without hard-coding a
seq_file implementation detail.


Note You need to log in before you can comment on or make changes to this bug.