Availability impact via omitted iterator count
Published May 28, 2026 · Updated May 28, 2026
Uninitialized-data handling in Linux Kernel allows local users to cause an unspecified availability impact through the vsockmon interface. The non-linear skb path in virtio_transport_build_skb() manually zero-initializes an iov_iter without setting count, leaving the copy length at zero and the tap skb payload uninitialized. Affected releases span 6.7 through 6.12.89, 6.13 through 6.18.31, 6.19 through 7.0.8, and 7.1-rc1 through 7.1-rc3; local low-privileged access and a non-linear socket buffer are required, and the public record does not identify the resulting interruption as a hang, crash, reboot, or shutdown.
Summary
What happened
Uninitialized-data handling in Linux Kernel allows local users to cause an unspecified availability impact through the vsockmon interface. The non-linear skb path in virtio_transport_build_skb() manually zero-initializes an iov_iter without setting count, leaving the copy length at zero and the tap skb payload uninitialized. Affected releases span 6.7 through 6.12.89, 6.13 through 6.18.31, 6.19 through 7.0.8, and 7.1-rc1 through 7.1-rc3; local low-privileged access and a non-linear socket buffer are required, and the public record does not identify the resulting interruption as a hang, crash, reboot, or shutdown.
The record
- CVE
- CVE-2026-46207
- Published
- May 28, 2026
- Updated
- May 28, 2026
- Vendor
- The Linux Kernel Organization
- Product
- Linux Kernel
- Classifications
- CWE-401
- Attack vector
- local
- Privileges
- authenticated
Timeline
How it unfolded
- May 28, 2026CVE publishedPublication date reported by the CVE source.
- May 28, 2026Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=4b0bf10eb077cb43c09746251ef3608d62c45667 <06747f52ab157591cec7e5623a759473b66ef6f6
- Affected versionversion=4b0bf10eb077cb43c09746251ef3608d62c45667 <378b131a25bd1a5ee27ca199fe486c299d5350c5
- Affected versionversion=4b0bf10eb077cb43c09746251ef3608d62c45667 <3a3e3d90cbc79600544536723911657730759af3
- Affected versionversion=4b0bf10eb077cb43c09746251ef3608d62c45667 <52da6a74ca3de0fcda60301096b71534b3b18641
- Affected versionversion=6.7
What conditions does exploitation require?
What is affected?
Published CVSS scores
CVSS describes severity. EPSS estimates exploitation probability.
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Weakness, pattern, technique
Public exploit references
No public exploit references are available in this record.
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo