1223123 – (CVE-2024-26887) VUL-0: CVE-2024-26887: kernel: Bluetooth: btusb: Fix memory leak

Bug 1223123 (CVE-2024-26887) - VUL-0: CVE-2024-26887: kernel: Bluetooth: btusb: Fix memory leak

Summary: VUL-0: CVE-2024-26887: kernel: Bluetooth: btusb: Fix memory leak

Status:	RESOLVED FIXED

Alias:	CVE-2024-26887

Product:	SUSE Security Incidents
Classification:	Novell Products
Component:	Incidents (show other bugs)
Version:	unspecified
Hardware:	Other Other

Priority:	P5 - None Severity: Normal
Target Milestone:	---
Assignee:	Kernel Bugs
QA Contact:	Security Team bot

URL:	https://smash.suse.de/issue/402296/
Whiteboard:	CVSSv3.1:SUSE:CVE-2024-26887:5.5:(AV:...
Keywords:

Depends on:
Blocks:

Clone This Bug

Reported:	2024-04-19 09:18 UTC by SMASH SMASH
Modified:	2024-04-19 09:19 UTC (History)
CC List:	1 user (show)

See Also:
Found By:	Security Response Team
Services Priority:
Business Priority:
Blocker:	---
Marketing QA Status:	---
IT Deployment:	---

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.

Description SMASH SMASH 2024-04-19 09:18:42 UTC

In the Linux kernel, the following vulnerability has been resolved:

Bluetooth: btusb: Fix memory leak

This checks if CONFIG_DEV_COREDUMP is enabled before attempting to clone
the skb and also make sure btmtk_process_coredump frees the skb passed
following the same logic.

References:
http://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2024-26887
https://git.kernel.org/pub/scm/linux/security/vulns.git/plain/cve/published/2024/CVE-2024-26887.mbox
https://git.kernel.org/stable/c/620b9e60e4b55fa55540ce852a0f3c9e6091dbbc
https://git.kernel.org/stable/c/b10e6f6b160a60b98fb7476028f5a95405bbd725
https://git.kernel.org/stable/c/b08bd8f02a24e2b82fece5ac51dc1c3d9aa6c404
https://git.kernel.org/stable/c/79f4127a502c5905f04da1f20a7bbe07103fb77c
https://www.cve.org/CVERecord?id=CVE-2024-26887
https://bugzilla.redhat.com/show_bug.cgi?id=2275676

Comment 1 Alexander Bergmann 2024-04-19 09:19:10 UTC

None of our SLE or openSUSE kernels are affected.