gve: fix napi_disable deadlock when attempting to disable XSK pools
- 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.18.57, 7.2.11
- 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: gve: fix napi_disable deadlock when attempting to disable XSK pools When disabling XSK pools, GVE calls the unlocked versions of napi_disable and napi_enable. However, the netdev lock has already been acquired before ndo_bpf is called because GVE supports queue management ops. Calling the unlocked versions of napi_disable/enable results in a deadlock when attempting to disable XSK pools, as the thread attempts to re-acquire a lock it already holds. Update the NAPI calls to use the locked versions. This issue was found in production.
Timeline
- CVE published
- First seen by cve.now
Affected versions
- Linux Linux
From 606048cbd8346e616cfaee01b0143d072534136d · fixed in 42935a61001927aa01db10b53b420efd37eaa99b; From 606048cbd8346e616cfaee01b0143d072534136d · fixed in 3d377911ce81fd4e61af814e750d8e08879a5208; From 606048cbd8346e616cfaee01b0143d072534136d · fixed in 0cb6939a4dfefa822007b7a71986e06bc4f61f54
- Linux Linux
6.16
- KernelLinux
From 6.16.0 · fixed in 6.18.57; From 6.19.0 · fixed in 7.2.11