CVE-2024-47809: Linux kernel · dlm: fix possible lkb_resource null dereference
Affects Linux kernelSource GCVE Database
Not known to be exploited · CVSS 5.5 Medium · fixed in 5.15.0-1112.119~20.04.1 : update Linux kernel when convenient.
Data as of 26 Oct 2026, 16:39 UTC
- EPSS
- 0.2% chance of exploitation in 30 days – higher than 15% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
- Patch
- Available – fixed in 5.15.0-1112.119~20.04.1, 5.15.0-1117.126~20.04.1, 5.15.0-1117.126~20.04.2 +63
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:HExploitation evidence
Disclosed: evidence found.
CVE published 11 Jan 2025
Detectable: no evidence on record.
No public nuclei template indexed
Weaponised: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors
A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 26 Oct 2026.
What to do
Upgrade to a fixed release listed under Affected software.
Patches and advisories
- ubuntu.com/security/notices/USN-7379-1 (opens in a new tab)
- ubuntu.com/security/notices/USN-7380-1 (opens in a new tab)
- ubuntu.com/security/notices/USN-7381-1 (opens in a new tab)
- ubuntu.com/security/notices/USN-7382-1 (opens in a new tab)
- ubuntu.com/security/notices/USN-7379-2 (opens in a new tab)
- ubuntu.com/security/notices/USN-7449-1 (opens in a new tab)
- ubuntu.com/security/notices/USN-7450-1 (opens in a new tab)
- ubuntu.com/security/notices/USN-7451-1 (opens in a new tab)
- ubuntu.com/security/notices/USN-7452-1 (opens in a new tab)
- ubuntu.com/security/notices/USN-7453-1 (opens in a new tab)
- ubuntu.com/security/notices/USN-7449-2 (opens in a new tab)
- ubuntu.com/security/notices/USN-7468-1 (opens in a new tab)
Affected software
| Product | Affected | Fixed in |
|---|---|---|
Ubuntu 24.04 LTSlinuxpkg:deb/ubuntu/linux?arch=source&distro=nobleOther threats | Affected
| Fixed in
|
Ubuntu 24.04 LTSlinux-awspkg:deb/ubuntu/linux-aws?arch=source&distro=nobleOther threats | Affected
| Fixed in
|
Ubuntu 24.04 LTSlinux-azurepkg:deb/ubuntu/linux-azure?arch=source&distro=nobleOther threats | Affected
| Fixed in
|
Ubuntu 24.04 LTSlinux-azure-6.11pkg:deb/ubuntu/linux-azure-6.11?arch=source&distro=nobleOther threats | Affected
| Fixed in
|
Ubuntu 24.04 LTSlinux-azure-nvidiapkg:deb/ubuntu/linux-azure-nvidia?arch=source&distro=nobleOther threats | Affected
| Fixed in
|
Ubuntu 24.04 LTSlinux-gcppkg:deb/ubuntu/linux-gcp?arch=source&distro=nobleOther threats | Affected
| Fixed in
|
Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.
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.
References
- ubuntu.com/security/CVE-2024-47809 (opens in a new tab)
- cve.org/CVERecord?id=CVE-2024-47809 (opens in a new tab)
- git.kernel.org/linus/b98333c67daf887c724cd692e88e2db9418c0861 (opens in a new tab)
- git.kernel.org/stable/c/2db11504ef82a60c1a2063ba7431a5cd013ecfcb (opens in a new tab)
- git.kernel.org/stable/c/6fbdc3980b70e9c1c86eccea7d5ee68108008fa7 (opens in a new tab)
- git.kernel.org/stable/c/b98333c67daf887c724cd692e88e2db9418c0861 (opens in a new tab)
- ubuntu.com/security/notices/USN-7379-1 (opens in a new tab)
- ubuntu.com/security/notices/USN-7380-1 (opens in a new tab)
- ubuntu.com/security/notices/USN-7381-1 (opens in a new tab)
- ubuntu.com/security/notices/USN-7382-1 (opens in a new tab)
- ubuntu.com/security/notices/USN-7379-2 (opens in a new tab)
- ubuntu.com/security/notices/USN-7449-1 (opens in a new tab)
- ubuntu.com/security/notices/USN-7450-1 (opens in a new tab)
- ubuntu.com/security/notices/USN-7451-1 (opens in a new tab)
- ubuntu.com/security/notices/USN-7452-1 (opens in a new tab)
- ubuntu.com/security/notices/USN-7453-1 (opens in a new tab)
- ubuntu.com/security/notices/USN-7449-2 (opens in a new tab)
- ubuntu.com/security/notices/USN-7468-1 (opens in a new tab)
- ubuntu.com/security/notices/USN-7523-1 (opens in a new tab)
- ubuntu.com/security/notices/USN-7524-1 (opens in a new tab)