dmaengine: idxd: Fix possible invalid memory access after FLR
- 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.21, 6.19.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
- Exploitation: none
- Automatable: no
- Technical impact: total
Summary
In the Linux kernel, the following vulnerability has been resolved: dmaengine: idxd: Fix possible invalid memory access after FLR In the case that the first Function Level Reset (FLR) concludes correctly, but in the second FLR the scratch area for the saved configuration cannot be allocated, it's possible for a invalid memory access to happen. Always set the deallocated scratch area to NULL after FLR completes.
Timeline
- CVE published
- CISA SSVC assessment
Exploitation: none · Automatable: no · Technical impact: total
- Record last updated
Affected versions
- Linux Linux
From 98d187a989036096feaa2fef1ec3b2240ecdeacf · fixed in 504c0e6751001ac46917c73e703f2b1b92cfc026; From 98d187a989036096feaa2fef1ec3b2240ecdeacf · fixed in 867d0c801f21370d561420fa32f2ea1a7dc3a22d; From 98d187a989036096feaa2fef1ec3b2240ecdeacf · fixed in d6077df7b75d26e4edf98983836c05d00ebabd8d
- Linux Linux
6.14
- KernelLinux
From 6.14.0 · fixed in 6.18.21; From 6.19.0 · fixed in 6.19.11