accel/ivpu: Add bounds checks for firmware log indices
- 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.94, 6.18.36, 7.0.13
- 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: partial
Summary
In the Linux kernel, the following vulnerability has been resolved: accel/ivpu: Add bounds checks for firmware log indices Add validation that read and write indices in the firmware log buffer are within valid bounds (< data_size) before using them. If out-of-bounds indices are encountered (from firmware), clamp them to safe values instead of proceeding with invalid offsets. This prevents potential out-of-bounds buffer access when firmware supplies invalid log indices.
Timeline
- CVE published
- CISA SSVC assessment
Exploitation: none · Automatable: no · Technical impact: partial
- Record last updated
Affected versions
- Linux Linux
From 0923a7d55a85179744926b7c11768a81679cc4d4 · fixed in 5961c703414048f46818be8bbb11075a9a63fb4e; From 1fc1251149a76d3b75d7f4c94d9c4e081b7df6b4 · fixed in 8ec70c0dbdf04392a26e03e38798a373934177be; From 1fc1251149a76d3b75d7f4c94d9c4e081b7df6b4 · fixed in 535da9ad8420c3b686a642403d4147ff220255fd; From 1fc1251149a76d3b75d7f4c94d9c4e081b7df6b4 · fixed in dd1311bcf0e62f0c515115f46a3813370f4a4bb1; From 6.12.30 · fixed in 6.12.94
- Linux Linux
6.13
- KernelLinux
fixed in 6.12.94; From 6.13.0 · fixed in 6.18.36; fixed in 7.0.13