Bug 2281893 (CVE-2024-35972) - CVE-2024-35972 kernel: bnxt_en: Fix possible memory leak in bnxt_rdma_aux_device_init()
Summary: CVE-2024-35972 kernel: bnxt_en: Fix possible memory leak in bnxt_rdma_aux_dev...
Keywords:
Status: NEW
Alias: CVE-2024-35972
Product: Security Response
Classification: Other
Component: vulnerability
Version: unspecified
Hardware: All
OS: Linux
low
low
Target Milestone: ---
Assignee: Product Security
QA Contact:
URL:
Whiteboard:
Depends On: 2281894
Blocks: 2282028
TreeView+ depends on / blocked
 
Reported: 2024-05-20 16:32 UTC by Robb Gatica
Modified: 2024-06-09 17:23 UTC (History)
50 users (show)

Fixed In Version: kernel 6.6.28, kernel 6.8.7, kernel 6.9
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed:
Embargoed:


Attachments (Terms of Use)

Description Robb Gatica 2024-05-20 16:32:55 UTC
In the Linux kernel, the following vulnerability has been resolved:

bnxt_en: Fix possible memory leak in bnxt_rdma_aux_device_init()

The Linux kernel CVE team has assigned CVE-2024-35972 to this issue.

Upstream advisory:
https://lore.kernel.org/linux-cve-announce/2024052023-CVE-2024-35972-138d@gregkh/T

Comment 1 Robb Gatica 2024-05-20 16:33:33 UTC
Created kernel tracking bugs for this issue:

Affects: fedora-all [bug 2281894]

Comment 3 Michal Schmidt 2024-05-31 07:58:38 UTC
A cure worse than the disease. The upstream patch changes a theoretical memory leak to a NULL pointer dereference (aux_priv->edev is zero-initialized, in bnxt_aux_dev_release aux_priv->edev->net will be NULL and the function will dereference it). 

And, as is often the case with Linux kernel CVEs about memory allocation error paths, the bug will never happen in practice, because tiny GFP_KERNEL allocations *never* fail in the Linux kernel.

Comment 4 Alex 2024-06-09 17:23:43 UTC
The result of automatic check (that is developed by Alexander Larkin) for this CVE-2024-35972 is: CHECK	Maybe valid. Check manually. with impact LOW (that is an approximation based on flags REMOTE INIT SIMPLEFIX LEAK NETWORK IMPROVEONLY  ; these flags parsed automatically based on patch 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.