nfp: hold IPsec RX state under the XArray lock
- 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.6.158, 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: nfp: hold IPsec RX state under the XArray lock nfp_net_ipsec_rx() drops the XArray lock before taking a reference to the xfrm_state it found. The delete path can erase the entry and drop the last state reference in that interval. RX can then try to increment a zero refcount after the state has been queued for destruction. The driver queues firmware invalidation asynchronously; the delete path does not wait for the command to complete or drain pending RX processing. The XFRM garbage collector waits for an RCU grace period before freeing the state. That delays reclamation but does not make acquiring a reference from zero valid. Take the xfrm_state reference before releasing the XArray lock so xa_erase() cannot run between lookup and reference acquisition.
Timeline
- CVE published
- Record last updated
Affected versions
- Linux Linux
From 57f273adbcd44172cbe0bd10b8b7408dd255699f · fixed in c1b1639fb138db52fcfbd1747e92f2454076c6d5; From 57f273adbcd44172cbe0bd10b8b7408dd255699f · fixed in dd765023bb54f9650f8b9137906fb2c4a554dd1d; From 57f273adbcd44172cbe0bd10b8b7408dd255699f · fixed in 8468d05aa08dc430b5675beadf6f6fb8943f170b; From 57f273adbcd44172cbe0bd10b8b7408dd255699f · fixed in fe6c8ea8bfd5d1253bb0de682b1fcc2c4bb92488; From 57f273adbcd44172cbe0bd10b8b7408dd255699f · fixed in 1a983a4e14c635c40354be110cd9a1a5c94e01e6
- Linux Linux
6.2
- KernelLinux
From 6.2.0 · fixed in 6.6.158; From 6.7.0 · fixed in 6.12.112; From 6.13.0 · fixed in 6.18.55; From 6.19.0 · fixed in 7.2.9