xsk: validate metadata when processing requests
- Published
- Last modified
- Where the record stands: published, rejected by its publisher, or superseded by another id.What do these mean? →
- published
- Whether CISA lists it in its Known Exploited Vulnerabilities catalog: proof that attackers are using it.What do these mean? →
- Not listed in CISA KEV
- Fix
- Fixed in 6.15, 6.18.45, 7.1.9
- Whether working attack code is public (Exploit-DB, Metasploit, Nuclei or GitHub). Public code makes attacks easier.What do these mean? →
- None on Exploit-DB, Metasploit or GitHub
- Exploitation: none
- Automatable: no
- Technical impact: total
Summary
In the Linux kernel, the following vulnerability has been resolved: xsk: validate metadata when processing requests The zero-copy path validates TX metadata while obtaining the descriptor context, then reads it again later when preparing the hardware request. User space can change the metadata between those operations and bypass the original validation. Validate the metadata in xsk_tx_metadata_request() and use the resulting flags snapshot for every feature check. Read request fields once so all zero-copy drivers process only values observed after successful validation.
Timeline
- CVE published
- CISA SSVC assessment
Exploitation: none · Automatable: no · Technical impact: total
- Record last updated
Affected versions
- Linux Linux
From ca4419f15abd19ba8be1e109661b60f9f5b6c9f0 · fixed in 5fd121971912dee2f5af1efec64462ac722deb17; From ca4419f15abd19ba8be1e109661b60f9f5b6c9f0 · fixed in 0cc7aa6e0d19027fdd42e6fbd156267ac1e3bbba; From ca4419f15abd19ba8be1e109661b60f9f5b6c9f0 · fixed in 849b1664dbda1cf6c63e0fd4f9dec23782b8c851; From 6.14.2 · fixed in 6.15
- Linux Linux
6.15
- KernelLinux
From 6.15.0 · fixed in 6.18.45; From 6.19.0 · fixed in 7.1.9