net/ionic: avoid OOB TX partner lookup for hwstamp RXQ
- 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.12.106, 6.18.47, 7.1.11, 7.2.1
- 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
Summary
In the Linux kernel, the following vulnerability has been resolved: net/ionic: avoid OOB TX partner lookup for hwstamp RXQ The dedicated hardware timestamp RX queue is allocated with q->index equal to lif->ionic->nrxqs_per_lif. The normal txqcqs array only contains the regular queue pairs, so using that index to set rxq->partner can read one entry past txqcqs[] and then write through the derived pointer. Only link RX/TX partners for normal queue-pair indexes. Leave the hwstamp RX queue unpaired, and make the XDP_TX path abort cleanly if an RX queue has no TX partner.
Timeline
- CVE published
- Record last updated
Affected versions
- Linux Linux
From 8eeed8373e1cca836799bf8e4a05cffa8e444908 · fixed in 881a805a8029ba48c0ce81c6674910f8d83f7afb; From 8eeed8373e1cca836799bf8e4a05cffa8e444908 · fixed in 39fc615e355b65b8d43be30da57aa95ae6eaf688; From 8eeed8373e1cca836799bf8e4a05cffa8e444908 · fixed in f3868046e8e2e761d4d943a232bd109ff22a7d5b; From 8eeed8373e1cca836799bf8e4a05cffa8e444908 · fixed in ea081b4435515ac7177eb598a3c0678d1b9e7911; From 8eeed8373e1cca836799bf8e4a05cffa8e444908 · fixed in d92255b405fb6f5acca408239ccd742e0a42c9cb
- Linux Linux
6.9
- KernelLinux
From 6.9.0 · fixed in 6.12.106; From 6.13.0 · fixed in 6.18.47; From 6.19.0 · fixed in 7.1.11; From 7.2.0 · fixed in 7.2.1