dlm: fix possible lkb_resource null dereference
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.
CVE-2024-47809
Primary source · Revision 1
Imported from structured advisory data. Source references identify upstream records or fields; verify affected versions and your deployed configuration.
Security context
Source reference: cve:CVE-2024-47809
Linux
Source reference: /containers/cna/affected/0/product
- Affected versions
- Not stated in this record
- Fixed versions
- Not stated in this record
- Prerequisites
- Not stated in this record
Linux
Source reference: /containers/cna/affected/1/product
- Affected versions
- Not stated in this record
- Fixed versions
- Not stated in this record
- Prerequisites
- Not stated in this record
Structured affected-version data
Original package identities and version rules from this source.
[
{
"repo": "https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git",
"vendor": "Linux",
"product": "Linux",
"versions": [
{
"status": "affected",
"version": "43279e5376017c40b4be9af5bc79cbb4ef6f53d7",
"lessThan": "e1ffea6bec96d4349dbfcc42ad3e436259f64243",
"versionType": "git"
},
{
"status": "affected",
"version": "43279e5376017c40b4be9af5bc79cbb4ef6f53d7",
"lessThan": "8d55ce46dd543c6965970ce70c22c3076dd35b1e",
"versionType": "git"
},
{
"status": "affected",
"version": "43279e5376017c40b4be9af5bc79cbb4ef6f53d7",
"lessThan": "6fbdc3980b70e9c1c86eccea7d5ee68108008fa7",
"versionType": "git"
},
{
"status": "affected",
"version": "43279e5376017c40b4be9af5bc79cbb4ef6f53d7",
"lessThan": "2db11504ef82a60c1a2063ba7431a5cd013ecfcb",
"versionType": "git"
},
{
"status": "affected",
"version": "43279e5376017c40b4be9af5bc79cbb4ef6f53d7",
"lessThan": "b98333c67daf887c724cd692e88e2db9418c0861",
"versionType": "git"
}
],
"programFiles": [
"fs/dlm/lock.c"
],
"defaultStatus": "unaffected"
},
{
"repo": "https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git",
"vendor": "Linux",
"product": "Linux",
"versions": [
{
"status": "affected",
"version": "2.6.30"
},
{
"status": "unaffected",
"version": "0",
"lessThan": "2.6.30",
"versionType": "semver"
},
{
"status": "unaffected",
"version": "5.15.209",
"versionType": "semver",
"lessThanOrEqual": "5.15.*"
},
{
"status": "unaffected",
"version": "6.1.167",
"versionType": "semver",
"lessThanOrEqual": "6.1.*"
},
{
"status": "unaffected",
"version": "6.6.66",
"versionType": "semver",
"lessThanOrEqual": "6.6.*"
},
{
"status": "unaffected",
"version": "6.12.5",
"versionType": "semver",
"lessThanOrEqual": "6.12.*"
},
{
"status": "unaffected",
"version": "6.13",
"versionType": "original_commit_for_fix",
"lessThanOrEqual": "*"
}
],
"programFiles": [
"fs/dlm/lock.c"
],
"defaultStatus": "affected"
}
]- Related CVEs
- CVE-2024-47809
Source reference:
/cveMetadata/cveId
Publisher severity
No explicit severity was provided.
- Event
- #26742 · Revision 1
- Added to Heist Feed
- Publisher date