ALSA: pcm: Don't setup bogus iov_iter for silencing
- 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.142, 6.12.92, 6.18.34, 7.0.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: ALSA: pcm: Don't setup bogus iov_iter for silencing At transition to the iov_iter for PCM data transfer, we blindly applied the iov_iter setup also for silencing (i.e. data = NULL), and it leads to a calculation of bogus iov_iter. Fortunately this didn't cause troubles on most of architectures but it goes wrong on RISC-V now, causing a NULL dereference. Handle the NULL data case to treat the silencing in interleaved_copy() for addressing the bug above. noninterleaved_copy() has already the NULL data handling, so it doesn't need changes.
Timeline
- CVE published
- CISA SSVC assessment
Exploitation: none · Automatable: no · Technical impact: total
- Record last updated
Affected versions
- Linux Linux
From cf393babb37a1679a1ec1d864df1090353465e23 · fixed in 41a766c647294842c9b17672449f8e011048cba9; From cf393babb37a1679a1ec1d864df1090353465e23 · fixed in ce836587e594af39ff048d9b29dee0f5f10692c9; From cf393babb37a1679a1ec1d864df1090353465e23 · fixed in feff0251386aa6bb180a0a1cf7c1f91ba868113d; From cf393babb37a1679a1ec1d864df1090353465e23 · fixed in c9f6768515818d71bdfc20119a81f3332c53b9c6; From cf393babb37a1679a1ec1d864df1090353465e23 · fixed in e4d3386b74fba8e01280484b67ee481ece00201e
- Linux Linux
6.6
- KernelLinux
From 6.6.0 · fixed in 6.6.142; From 6.7.0 · fixed in 6.12.92; From 6.13.0 · fixed in 6.18.34; From 6.19.0 · fixed in 7.0.11