eth: fbnic: Handle maximum standalone channels
- 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.112, 6.18.55, 7.2.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
Summary
In the Linux kernel, the following vulnerability has been resolved: eth: fbnic: Handle maximum standalone channels Standalone channels use one NAPI vector for each Tx and Rx queue. fbnic's allocation path excludes FBNIC_MAX_TXQS from that layout. A 64-Tx/64-Rx configuration therefore records 128 vectors but allocates only 64, leaving NULL entries that resource setup dereferences. Include the maximum vector count in standalone allocation.
Timeline
- CVE published
- Record last updated
Affected versions
- Linux Linux
From bc6107771bb4be3009168cfda24d22131c026fe8 · fixed in 9843e5fabd6ab296df9c025b1d0e5bf79a6b8a08; From bc6107771bb4be3009168cfda24d22131c026fe8 · fixed in 6c903188b67617070017305a325fa326f270a43d; From bc6107771bb4be3009168cfda24d22131c026fe8 · fixed in 16ff1023213cc39c1a7ce737205c2a1a53c3a716; From bc6107771bb4be3009168cfda24d22131c026fe8 · fixed in 1f4c73064a50f53d596c6f1d06d2d700f43c4b32
- Linux Linux
6.11
- KernelLinux
From 6.11.0 · fixed in 6.12.112; From 6.13.0 · fixed in 6.18.55; From 6.19.0 · fixed in 7.2.9