net/ionic: avoid OOB TX partner lookup for hwstamp RXQ
No exploitation in the wild has been reported. EPSS puts the chance of exploitation in the next 30 days at 0%. Fixed in Kernel f3868046e8e2e761d4d943a232bd109ff22a7d5b, Kernel 39fc615e355b65b8d43be30da57aa95ae6eaf688, Kernel 881a805a8029ba48c0ce81c6674910f8d83f7afb and 6 more.
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.
Affected
Vendors, products and packages with version ranges
| Vendor | Product | Versions | Fixed |
|---|---|---|---|
| Linux | Kernel | >=8eeed8373e1cca836799bf8e4a05cffa8e444908 <f3868046e8e2e761d4d943a232bd109ff22a7d5b, >=8eeed8373e1cca836799bf8e4a05cffa8e444908 <39fc615e355b65b8d43be30da57aa95ae6eaf688, >=8eeed8373e1cca836799bf8e4a05cffa8e444908 <881a805a8029ba48c0ce81c6674910f8d83f7afb, >=8eeed8373e1cca836799bf8e4a05cffa8e444908 <d92255b405fb6f5acca408239ccd742e0a42c9cb, >=8eeed8373e1cca836799bf8e4a05cffa8e444908 <ea081b4435515ac7177eb598a3c0678d1b9e7911, =6.9 | f3868046e8e2e761d4d943a232bd109ff22a7d5b, 39fc615e355b65b8d43be30da57aa95ae6eaf688, 881a805a8029ba48c0ce81c6674910f8d83f7afb, d92255b405fb6f5acca408239ccd742e0a42c9cb, ea081b4435515ac7177eb598a3c0678d1b9e7911 |
| linux-kernel: Kernel | >=6.19.0 <7.1.11, >=6.9.0 <6.12.106, >=7.2.0 <7.2.1, >=6.13.0 <6.18.47 | 7.1.11, 6.12.106, 7.2.1, 6.18.47 |
Timeline
Every event on this vulnerability
Related
Other vulnerabilities in Kernel, strongest first
Embed
A live severity badge for an advisory, README or ticket