Bug 2269181 (CVE-2023-52493) - CVE-2023-52493 kernel: bus: mhi: host: Drop chan lock before queuing buffers
Summary: CVE-2023-52493 kernel: bus: mhi: host: Drop chan lock before queuing buffers
Keywords:
Status: NEW
Alias: CVE-2023-52493
Product: Security Response
Classification: Other
Component: vulnerability
Version: unspecified
Hardware: All
OS: Linux
medium
medium
Target Milestone: ---
Assignee: Product Security
QA Contact:
URL:
Whiteboard:
Depends On: 2269182
Blocks: 2269239
TreeView+ depends on / blocked
 
Reported: 2024-03-12 15:49 UTC by Marco Benatto
Modified: 2024-06-09 15:28 UTC (History)
50 users (show)

Fixed In Version: kernel 5.10.210, kernel 5.15.149, kernel 6.1.76, kernel 6.6.15, kernel 6.7.3, kernel 6.8-rc1
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed:
Embargoed:

Attachments (Terms of Use)

Description Marco Benatto 2024-03-12 15:49:35 UTC 
In the Linux kernel, the following vulnerability has been resolved:

bus: mhi: host: Drop chan lock before queuing buffers

The Linux kernel CVE team has assigned CVE-2023-52493 to this issue.

Upstream advisory:
https://lore.kernel.org/linux-cve-announce/20240229155245.1571576-34-lee@kernel.org/T
Comment 1 Marco Benatto 2024-03-12 15:50:14 UTC 
Created kernel tracking bugs for this issue:

Affects: fedora-all [bug 2269182]
Comment 2 Justin M. Forbes 2024-03-26 16:47:24 UTC 
This was fixed for Fedora with the 6.7.3 stable kernel updates.
Comment 3 Alex 2024-06-09 15:28:32 UTC 
The result of automatic check (that is developed by Alexander Larkin) for this CVE-2023-52493 is: CHECK	Maybe valid. Check manually. with impact MODERATE (that is approximation based on flags LOCK SIMPLEFIX  ; these flags parsed automatically based on patche data). Such automatic check happens only for Low/Moderates (and only when not from reporter, but parsing already existing CVE). Highs always checked manually (I check it myself and then we check it again in Remediation team). In rare cases some of the Moderates could be increased to High later.
Note You need to log in before you can comment on or make changes to this bug.