espintcp: Fix race condition in espintcp_close()
- 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.75, 6.18.16, 6.19.6
- 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
- Exploitation: none
- Automatable: no
- Technical impact: total
Summary
In the Linux kernel, the following vulnerability has been resolved: espintcp: Fix race condition in espintcp_close() This issue was discovered during a code audit. After cancel_work_sync() is called from espintcp_close(), espintcp_tx_work() can still be scheduled from paths such as the Delayed ACK handler or ksoftirqd. As a result, the espintcp_tx_work() worker may dereference a freed espintcp ctx or sk. The following is a simple race scenario: cpu0 cpu1 espintcp_close() cancel_work_sync(&ctx->work); espintcp_write_space() schedule_work(&ctx->work); To prevent this race condition, cancel_work_sync() is replaced with disable_work_sync().
Timeline
- CVE published
- CISA SSVC assessment
Exploitation: none · Automatable: no · Technical impact: total
- Record last updated
Affected versions
- Linux Linux
From e27cca96cd68fa2c6814c90f9a1cfd36bb68c593 · fixed in f7ad8b1d0e421c524604d5076b73232093490d5c; From e27cca96cd68fa2c6814c90f9a1cfd36bb68c593 · fixed in 664e9df53226b4505a0894817ecad2c610ab11d8; From e27cca96cd68fa2c6814c90f9a1cfd36bb68c593 · fixed in 022ff7f347588de6e17879a1da6019647b21321b; From e27cca96cd68fa2c6814c90f9a1cfd36bb68c593 · fixed in e1512c1db9e8794d8d130addd2615ec27231d994
- Linux Linux
5.6
- KernelLinux
From 5.6.0 · fixed in 6.12.75; From 6.13.0 · fixed in 6.18.16; From 6.19.0 · fixed in 6.19.6