Linux Kernel up to 5.10.172/5.15.98/6.1.15/6.2.2 dev_kfree_skb memory leak

CVSS Meta Temp Score
CVSS is a standardized scoring system to determine possibilities of attacks. The Temp Score considers temporal factors like disclosure, exploit and countermeasures. The unique Meta Score calculates the average score of different sources to provide a normalized scoring system.
Current Exploit Price (≈)
Our analysts are monitoring exploit markets and are in contact with vulnerability brokers. The range indicates the observed or calculated exploit price to be seen on exploit markets. A good indicator to understand the monetary effort required for and the popularity of an attack.
CTI Interest Score
Our Cyber Threat Intelligence team is monitoring different web sites, mailing lists, exploit markets and social media networks. The CTI Interest Score identifies the interest of attackers and the security community for this specific vulnerability in real-time. A high score indicates an elevated risk to be targeted for this vulnerability.
4.6$0-$5k0.00

Summaryinfo

A vulnerability, which was classified as critical, was found in Linux Kernel up to 5.10.172/5.15.98/6.1.15/6.2.2. This affects the function dev_kfree_skb. Such manipulation leads to memory leak. This vulnerability is documented as CVE-2023-54036. There is not any exploit available. You should upgrade the affected component.

Detailsinfo

A vulnerability, which was classified as critical, has been found in Linux Kernel up to 5.10.172/5.15.98/6.1.15/6.2.2. Affected by this issue is the function dev_kfree_skb. The manipulation with an unknown input leads to a memory leak vulnerability. Using CWE to declare the problem leads to CWE-401. The product does not sufficiently track and release allocated memory after it has been used, which slowly consumes remaining memory. Impacted is availability. CVE summarizes:

In the Linux kernel, the following vulnerability has been resolved: wifi: rtl8xxxu: Fix memory leaks with RTL8723BU, RTL8192EU The wifi + bluetooth combo chip RTL8723BU can leak memory (especially?) when it's connected to a bluetooth audio device. The busy bluetooth traffic generates lots of C2H (card to host) messages, which are not freed correctly. To fix this, move the dev_kfree_skb() call in rtl8xxxu_c2hcmd_callback() inside the loop where skb_dequeue() is called. The RTL8192EU leaks memory because the C2H messages are added to the queue and left there forever. (This was fine in the past because it probably wasn't sending any C2H messages until commit e542e66b7c2e ("wifi: rtl8xxxu: gen2: Turn on the rate control"). Since that commit it sends a C2H message when the TX rate changes.) To fix this, delete the check for rf_paths > 1 and the goto. Let the function process the C2H messages from RTL8192EU like the ones from the other chips. Theoretically the RTL8188FU could also leak like RTL8723BU, but it most likely doesn't send C2H messages frequently enough. This change was tested with RTL8723BU by Erhard F. I tested it with RTL8188FU and RTL8192EU.

The advisory is available at git.kernel.org. This vulnerability is handled as CVE-2023-54036 since 12/24/2025. The exploitation is known to be difficult. Technical details are known, but there is no available exploit.

The vulnerability scanner Nessus provides a plugin with the ID 279943 (Linux Distros Unpatched Vulnerability : CVE-2023-54036), which helps to determine the existence of the flaw in a target environment.

Upgrading to version 5.10.173, 5.15.99, 6.1.16 or 6.2.3 eliminates this vulnerability. Applying the patch 430f9f9bec53a75f9ccc53e156a66f13fc098b83/35fb0e275af1aa1ca0a9784417e90f988aaf8e78/93c3f34ec02fc81188d328287d4fddd498ccddea/f39a86b4efd270947ee252cc32a30b0aef492d65/b39f662ce1648db0b9de32e6a849b098480793cb is able to eliminate this problem. The bugfix is ready for download at git.kernel.org. The best possible mitigation is suggested to be upgrading to the latest version.

The vulnerability is also documented in the databases at Tenable (279943) and CERT Bund (WID-SEC-2025-2920). If you want to get best quality of vulnerability data, you may have to visit VulDB.

Affected

  • Open Source Linux Kernel

Productinfo

Type

Vendor

Name

Version

License

Website

CPE 2.3info

CPE 2.2info

CVSSv4info

VulDB Vector: 🔒
VulDB Reliability: 🔍

CVSSv3info

VulDB Meta Base Score: 4.8
VulDB Meta Temp Score: 4.6

VulDB Base Score: 4.8
VulDB Temp Score: 4.6
VulDB Vector: 🔒
VulDB Reliability: 🔍

CVSSv2info

AVACAuCIA
💳💳💳💳💳💳
💳💳💳💳💳💳
💳💳💳💳💳💳
VectorComplexityAuthenticationConfidentialityIntegrityAvailability
UnlockUnlockUnlockUnlockUnlockUnlock
UnlockUnlockUnlockUnlockUnlockUnlock
UnlockUnlockUnlockUnlockUnlockUnlock

VulDB Base Score: 🔒
VulDB Temp Score: 🔒
VulDB Reliability: 🔍

Exploitinginfo

Class: Memory leak
CWE: CWE-401 / CWE-404
CAPEC: 🔒
ATT&CK: 🔒

Physical: No
Local: No
Remote: Partially

Availability: 🔒
Status: Not defined

EPSS Score: 🔒
EPSS Percentile: 🔒

Price Prediction: 🔍
Current Price Estimation: 🔒

0-DayUnlockUnlockUnlockUnlock
TodayUnlockUnlockUnlockUnlock

Nessus ID: 279943
Nessus Name: Linux Distros Unpatched Vulnerability : CVE-2023-54036

Threat Intelligenceinfo

Interest: 🔍
Active Actors: 🔍
Active APT Groups: 🔍

Countermeasuresinfo

Recommended: Upgrade
Status: 🔍

0-Day Time: 🔒

Upgrade: Kernel 5.10.173/5.15.99/6.1.16/6.2.3
Patch: 430f9f9bec53a75f9ccc53e156a66f13fc098b83/35fb0e275af1aa1ca0a9784417e90f988aaf8e78/93c3f34ec02fc81188d328287d4fddd498ccddea/f39a86b4efd270947ee252cc32a30b0aef492d65/b39f662ce1648db0b9de32e6a849b098480793cb

Timelineinfo

12/24/2025 Advisory disclosed
12/24/2025 +0 days CVE reserved
12/24/2025 +0 days VulDB entry created
12/26/2025 +2 days VulDB entry last update

Sourcesinfo

Vendor: kernel.org

Advisory: git.kernel.org
Status: Confirmed

CVE: CVE-2023-54036 (🔒)
GCVE (CVE): GCVE-0-2023-54036
GCVE (VulDB): GCVE-100-338186
CERT Bund: WID-SEC-2025-2920 - Linux Kernel: Mehrere Schwachstellen

Entryinfo

Created: 12/24/2025 15:24
Updated: 12/26/2025 07:56
Changes: 12/24/2025 15:24 (58), 12/25/2025 10:54 (7), 12/26/2025 07:56 (2)
Complete: 🔍
Cache ID: 216::103

If you want to get best quality of vulnerability data, you may have to visit VulDB.

Discussion

No comments yet. Languages: en.

Please log in to comment.

Do you need the next level of professionalism?

Upgrade your account now!