CVE-2024-47730
crypto: hisilicon/qm - inject error before stopping queue
- 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
- 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
CISA's decision points: whether it is exploited, whether attacks can be automated, and how much control an attacker gets. Assessed (SSVC 2.0.3).What do these mean? →
- Exploitation: none
- Automatable: no
- Technical impact: partial
Summary
In the Linux kernel, the following vulnerability has been resolved: crypto: hisilicon/qm - inject error before stopping queue The master ooo cannot be completely closed when the accelerator core reports memory error. Therefore, the driver needs to inject the qm error to close the master ooo. Currently, the qm error is injected after stopping queue, memory may be released immediately after stopping queue, causing the device to access the released memory. Therefore, error is injected to close master ooo before stopping queue to ensure that the device does not access the released memory.
Timeline
- CVE published
- CISA SSVC assessment
Exploitation: none · Automatable: no · Technical impact: partial
- Record last updated
Affected versions
- Linux Linux
Version range not reported
- Linux Linux
5.8
References 7
git.kernel.org
- stable/c/85e81103033324d7a271dafb584991da39554a89
- stable/c/801d64177faaec184cee1e1aa4d8487df1364a54
- stable/c/98d3be34c9153eceadb56de50d9f9347e88d86e4
- stable/c/aa3e0db35a60002fb34ef0e4ad203aa59fd00203
- stable/c/f8024f12752e32ffbbf59e1c09d949f977ff743f
- stable/c/c5f5b813e546f7fe133539c3d7a5086cc8dd2aa1
- stable/c/b04f06fc0243600665b3b50253869533b7938468