btrfs: reinitialize delayed ref list after deleting it from the list
In the Linux kernel, the following vulnerability has been resolved: btrfs: reinitialize delayed ref list after deleting it from the list At insert_delayed_ref() if we need to update the action of an existing ref to BTRFS_DROP_DELAYED_REF, we delete the ref from its ref head's ref_add_list using list_del(), which leaves the ref's add_list member not reinitialized, as list_del() sets the next and prev members of the list to LIST_POISON1 and LIST_POISON2, respectively. If later we end up calling drop_delayed_ref() against the ref, which can happen during merging or when destroying delayed refs due to a transaction abort, we can trigger a crash since at drop_delayed_ref() we call list_empty() against the ref's add_list, which returns false since the list was not reinitialized after the list_del() and as a consequence we call list_del() again at drop_delayed_ref(). This results in an invalid list access since the next and prev members are set to poison pointers, resulting in a splat if CONFIG_LIST_HARDENED and CONFIG_DEBUG_LIST are set or invalid poison pointer dereferences otherwise. So fix this by deleting from the list with list_del_init() instead.
- Products
- Kernel
- Affected versions
- Not specified
- Fixed versions
- 4.19.324, 5.10.230, 5.15.172, 5.4.286, 6.1.117, 6.11.8, 6.6.61
- CVEs
- CVE-2024-50273
- Confirmed fixed CVEs
- Not specified
- Updated in this feed
- 7 Nov 2026, 02:14 UTC · Revision 1
Source evidence
btrfs: reinitialize delayed ref list after deleting it from the list
core-osv · Original sourcePublished 19 Nov 2024, 01:30 UTC
In the Linux kernel, the following vulnerability has been resolved: btrfs: reinitialize delayed ref list after deleting it from the list At insert_delayed_ref() if we need to update the action of an existing ref to BTRFS_DROP_DELAYED_REF, we delete the ref from its ref head's ref_add_list using list_del(), which leaves the ref's add_list member not reinitialized, as list_del() sets the next and prev members of the list to LIST_POISON1 and LIST_POISON2, respectively. If later we end up calling drop_delayed_ref() against the ref, which can happen during merging or when destroying delayed refs due to a transaction abort, we can trigger a crash since at drop_delayed_ref() we call list_empty() against the ref's add_list, which returns false since the list was not reinitialized after the list_del() and as a consequence we call list_del() again at drop_delayed_ref(). This results in an invalid list access since the next and prev members are set to poison pointers, resulting in a splat if CONFIG_LIST_HARDENED and CONFIG_DEBUG_LIST are set or invalid poison pointer dereferences otherwise. So fix this by deleting from the list with list_del_init() instead.
osv:CVE-2024-50273
Kernel
Fixed versions: 4.19.324, 5.4.286, 5.10.230, 5.15.172, 6.1.117, 6.6.61, 6.11.8
Complete source record
{
"id": "29c9a0404422786b01ce59be9f8e4f5b532c36a409076543b6c55d52d6d28d39",
"url": "https://osv.dev/vulnerability/CVE-2024-50273",
"method": "structured",
"payload": {
"kind": "advisory",
"title": "btrfs: reinitialize delayed ref list after deleting it from the list",
"summary": "In the Linux kernel, the following vulnerability has been resolved: btrfs: reinitialize delayed ref list after deleting it from the list At insert_delayed_ref() if we need to update the action of an existing ref to BTRFS_DROP_DELAYED_REF, we delete the ref from its ref head's ref_add_list using list_del(), which leaves the ref's add_list member not reinitialized, as list_del() sets the next and prev members of the list to LIST_POISON1 and LIST_POISON2, respectively. If later we end up calling drop_delayed_ref() against the ref, which can happen during merging or when destroying delayed refs due to a transaction abort, we can trigger a crash since at drop_delayed_ref() we call list_empty() against the ref's add_list, which returns false since the list was not reinitialized after the list_del() and as a consequence we call list_del() again at drop_delayed_ref(). This results in an invalid list access since the next and prev members are set to poison pointers, resulting in a splat if CONFIG_LIST_HARDENED and CONFIG_DEBUG_LIST are set or invalid poison pointer dereferences otherwise. So fix this by deleting from the list with list_del_init() instead.",
"evidence": "osv:CVE-2024-50273",
"products": [
{
"name": {
"value": "Kernel",
"evidence": "/affected/1/package/name"
},
"prerequisites": [],
"fixed_versions": [
{
"value": "4.19.324",
"evidence": "/affected/1/ranges"
},
{
"value": "5.4.286",
"evidence": "/affected/1/ranges"
},
{
"value": "5.10.230",
"evidence": "/affected/1/ranges"
},
{
"value": "5.15.172",
"evidence": "/affected/1/ranges"
},
{
"value": "6.1.117",
"evidence": "/affected/1/ranges"
},
{
"value": "6.6.61",
"evidence": "/affected/1/ranges"
},
{
"value": "6.11.8",
"evidence": "/affected/1/ranges"
}
],
"affected_versions": []
}
],
"severity": "high",
"structured": {
"id": "CVE-2024-50273",
"aliases": [
"CVE-2024-50273"
],
"metrics": [
{
"type": "CVSS_V3",
"score": "CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H"
}
],
"affected": [
{
"ranges": [
{
"repo": "https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git",
"type": "GIT",
"events": [
{
"introduced": "1d57ee941692d0cc928526e21a1557b2ae3e11db"
},
{
"fixed": "2fd0948a483e9cb2d669c7199bc620a21c97673d"
},
{
"fixed": "93c5b8decc0ef39ba84f4211d2db6da0a4aefbeb"
},
{
"fixed": "bf0b0c6d159767c0d1c21f793950d78486690ee0"
},
{
"fixed": "c24fa427fc0ae827b2a3a07f13738cbf82c3f851"
},
{
"fixed": "2cb1a73d1d44a1c11b0ee5eeced765dd80ec48e6"
},
{
"fixed": "f04be6d68f715c1473a8422fc0460f57b5e99931"
},
{
"fixed": "50a3933760b427759afdd23156a7280a19357a92"
},
{
"fixed": "c9a75ec45f1111ef530ab186c2a7684d0a0c9245"
}
]
}
],
"database_specific": {
"source": "https://storage.googleapis.com/cve-osv-conversion/osv-output/CVE-2024-50273.json"
}
},
{
"ranges": [
{
"type": "ECOSYSTEM",
"events": [
{
"introduced": "4.10.0"
},
{
"fixed": "4.19.324"
}
]
},
{
"type": "ECOSYSTEM",
"events": [
{
"introduced": "4.20.0"
},
{
"fixed": "5.4.286"
}
]
},
{
"type": "ECOSYSTEM",
"events": [
{
"introduced": "5.5.0"
},
{
"fixed": "5.10.230"
}
]
},
{
"type": "ECOSYSTEM",
"events": [
{
"introduced": "5.11.0"
},
{
"fixed": "5.15.172"
}
]
},
{
"type": "ECOSYSTEM",
"events": [
{
"introduced": "5.16.0"
},
{
"fixed": "6.1.117"
}
]
},
{
"type": "ECOSYSTEM",
"events": [
{
"introduced": "6.2.0"
},
{
"fixed": "6.6.61"
}
]
},
{
"type": "ECOSYSTEM",
"events": [
{
"introduced": "6.7.0"
},
{
"fixed": "6.11.8"
}
]
}
],
"package": {
"name": "Kernel",
"ecosystem": "Linux"
},
"database_specific": {
"source": "https://storage.googleapis.com/cve-osv-conversion/osv-output/CVE-2024-50273.json"
}
}
],
"modified": "2026-10-28T02:30:49.321521146Z",
"provider": "osv",
"references": [
"https://git.kernel.org/stable/c/2cb1a73d1d44a1c11b0ee5eeced765dd80ec48e6",
"https://git.kernel.org/stable/c/2fd0948a483e9cb2d669c7199bc620a21c97673d",
"https://git.kernel.org/stable/c/50a3933760b427759afdd23156a7280a19357a92",
"https://git.kernel.org/stable/c/93c5b8decc0ef39ba84f4211d2db6da0a4aefbeb",
"https://git.kernel.org/stable/c/bf0b0c6d159767c0d1c21f793950d78486690ee0",
"https://git.kernel.org/stable/c/c24fa427fc0ae827b2a3a07f13738cbf82c3f851",
"https://git.kernel.org/stable/c/c9a75ec45f1111ef530ab186c2a7684d0a0c9245",
"https://git.kernel.org/stable/c/f04be6d68f715c1473a8422fc0460f57b5e99931",
"https://lists.debian.org/debian-lts-announce/2025/01/msg00001.html",
"https://lists.debian.org/debian-lts-announce/2025/03/msg00002.html",
"https://github.com/CVEProject/cvelistV5/tree/main/cves/2024/50xxx/CVE-2024-50273.json",
"https://nvd.nist.gov/vuln/detail/CVE-2024-50273",
"https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git"
],
"provider_metadata": {
"cna_assigner": "Linux",
"osv_generated_from": "https://github.com/CVEProject/cvelistV5/tree/main/cves/2024/50xxx/CVE-2024-50273.json"
}
},
"related_cves": [
{
"value": "CVE-2024-50273",
"evidence": "/id"
}
],
"security_relevant": true,
"severity_evidence": "/severity/0/score"
},
"source_id": "core-osv",
"document_id": 517275,
"published_at": "2024-11-19T01:30:12.589+00:00"
}