CVE-2024-47809
Last modified
CVE-2024-47809 is a medium-severity vulnerability rated 5.5/10 on the CVSS scale. In the Linux kernel, the following vulnerability has been resolved: dlm: fix possible lkb_resource null dereference This patch fixes a possible null pointer dereference when this function is called from request_lock() as lkb->lkb_resource is not assigned yet, only after validate_lock_args() by calling attach_lkb(). Another issue is that a resource name could be a non printable bytearray and we cannot assume to be ASCII coded. The log functionality is probably never being hit when DLM is used in normal way and no debug logging is enabled. EPSS estimates a 0.22% chance of exploitation in the next 30 days.
Description
In the Linux kernel, the following vulnerability has been resolved: dlm: fix possible lkb_resource null dereference This patch fixes a possible null pointer dereference when this function is called from request_lock() as lkb->lkb_resource is not assigned yet, only after validate_lock_args() by calling attach_lkb(). Another issue is that a resource name could be a non printable bytearray and we cannot assume to be ASCII coded. The log functionality is probably never being hit when DLM is used in normal way and no debug logging is enabled. The null pointer dereference can only occur on a new created lkb that does not have the resource assigned yet, it probably never hits the null pointer dereference but we should be sure that other changes might not change this behaviour and we actually can hit the mentioned null pointer dereference. In this patch we just drop the printout of the resource name, the lkb id is enough to make a possible connection to a resource name if this exists.
Metrics
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H
Weakness Enumeration
Affected Software
| Vendor | Product | Versions |
|---|---|---|
| Linux | Linux Kernel | < 6.6.66 |
| Linux | Linux Kernel | >= 6.7, < 6.12.5 |
References
Timeline
- Published
- Last Modified
- Status
- Modified
Frequently Asked Questions
What is CVE-2024-47809?
How severe is CVE-2024-47809?
How do I fix CVE-2024-47809?
How Strix Helps
- How Strix found a critical auth bypass in etcdStrix autonomously discovered a critical authentication bypass in etcd, later designated CVE-2026-33413.
- Autonomous PentestingAI agents that find and validate exploitable vulnerabilities like this one across your applications.
- PR ReviewsPentest every pull request so vulnerable code is caught before it ships to production.
- AI Penetration TestingHow AI-driven penetration testing continuously covers your attack surface.
Related CVEs from 2024
- CVE-2024-47803Jenkins 2.478 and earlier, LTS 2.462.2 and earlier does not …4.3
- CVE-2024-47804If an attempt is made to create an item of a type prohibited…4.3
- CVE-2024-47805Jenkins Credentials Plugin 1380.va_435002fa_924 and earlier,…7.5
- CVE-2024-47806Jenkins OpenId Connect Authentication Plugin 4.354.v321ce67a…8.1
- CVE-2024-47807Jenkins OpenId Connect Authentication Plugin 4.354.v321ce67a…8.1
- CVE-2024-47808A vulnerability has been identified in SINEC NMS (All versio…6.5
- CVE-2024-4781A denial-of-service vulnerability was reported in some Lenov…6.5
- CVE-2024-47810A use-after-free vulnerability exists in the way Foxit Reade…8.8
- CVE-2024-47812ImportDump is an extension for mediawiki designed to automat…6
- CVE-2024-47813Wasmtime is an open source runtime for WebAssembly. Under ce…2.9
- CVE-2024-47814Vim is an open source, command line text editor. A use-after…4.7
- CVE-2024-47815IncidentReporting is a MediaWiki extension for moving incide…6
Are you affected by CVE-2024-47809?
Run a free Strix scan to check your systems for this vulnerability.
Scan your code nowSource: NVD / NIST
