GHSA-VRQ8-FR7J-453W
Vulnerability from github – Published: 2026-08-15 06:32 – Updated: 2026-08-15 06:32In the Linux kernel, the following vulnerability has been resolved:
bpf: fix crash in bpf_[set|remove]_dentry_xattr for negative dentries
bpf_set_dentry_xattr and bpf_remove_dentry_xattr BPF kfuncs attempt to lock the inode of the supplied dentry without checking if it is NULL. If a negative dentry is passed (e.g. from security_inode_create), d_inode(dentry) returns NULL, and inode_lock(inode) will cause a NULL pointer dereference.
Trivially fix this by adding a NULL check for inode before attempting to lock it, returning -EINVAL if it is NULL.
Additionally, drop WARN_ON(!inode) in bpf_xattr_read_permission() and bpf_xattr_write_permission(). These warnings could be triggered by passing a negative dentry to bpf_get_dentry_xattr() or the _locked variants of the xattr kfuncs, potentially causing a Denial of Service on systems with panic_on_warn enabled. Instead, simply return -EINVAL.
{
"affected": [],
"aliases": [
"CVE-2026-74400"
],
"database_specific": {
"cwe_ids": [],
"github_reviewed": false,
"github_reviewed_at": null,
"nvd_published_at": "2026-08-15T06:22:42Z",
"severity": null
},
"details": "In the Linux kernel, the following vulnerability has been resolved:\n\nbpf: fix crash in bpf_[set|remove]_dentry_xattr for negative dentries\n\nbpf_set_dentry_xattr and bpf_remove_dentry_xattr BPF kfuncs attempt to\nlock the inode of the supplied dentry without checking if it is\nNULL. If a negative dentry is passed (e.g. from\nsecurity_inode_create), d_inode(dentry) returns NULL, and\ninode_lock(inode) will cause a NULL pointer dereference.\n\nTrivially fix this by adding a NULL check for inode before attempting\nto lock it, returning -EINVAL if it is NULL.\n\nAdditionally, drop WARN_ON(!inode) in bpf_xattr_read_permission() and\nbpf_xattr_write_permission(). These warnings could be triggered by\npassing a negative dentry to bpf_get_dentry_xattr() or the _locked\nvariants of the xattr kfuncs, potentially causing a Denial of Service\non systems with panic_on_warn enabled. Instead, simply return -EINVAL.",
"id": "GHSA-vrq8-fr7j-453w",
"modified": "2026-08-15T06:32:32Z",
"published": "2026-08-15T06:32:32Z",
"references": [
{
"type": "ADVISORY",
"url": "https://nvd.nist.gov/vuln/detail/CVE-2026-74400"
},
{
"type": "WEB",
"url": "https://git.kernel.org/stable/c/0160edf2af51c5fde742973742c5d10497901b21"
},
{
"type": "WEB",
"url": "https://git.kernel.org/stable/c/07410646f6ff1d23222f105ccab778957d401bbe"
},
{
"type": "WEB",
"url": "https://git.kernel.org/stable/c/e003f3a4be738f650e283e92d07017c3fef8da52"
}
],
"schema_version": "1.4.0",
"severity": []
}
Sightings
| Author | Source | Type | Date | Other |
|---|
Nomenclature
- Seen: The vulnerability was mentioned, discussed, or observed by the user.
- Confirmed: The vulnerability has been validated from an analyst's perspective.
- Published Proof of Concept: A public proof of concept is available for this vulnerability.
- Exploited: The vulnerability was observed as exploited by the user who reported the sighting.
- Patched: The vulnerability was observed as successfully patched by the user who reported the sighting.
- Not exploited: The vulnerability was not observed as exploited by the user who reported the sighting.
- Not confirmed: The user expressed doubt about the validity of the vulnerability.
- Not patched: The vulnerability was not observed as successfully patched by the user who reported the sighting.
The approach is described in our paper Mapping CVEs to MITRE ATT&CK Techniques: A Curated Gold-Set Classifier and the Limits of LLM-Assisted Label Expansion.