tracing/user_events: Don't destroy fields when event removal fails
In the Linux kernel, the following vulnerability has been resolved: tracing/user_events: Don't destroy fields when event removal fails destroy_user_event() destroys the event's fields before attempting to remove the trace event call. If user_event_set_call_visible() fails, e.g. because the event is still enabled and trace_remove_event_call() returns -EBUSY, the event is left registered with an irreversibly destroyed field list. Any subsequent interaction with the event then operates on an empty field list while it is still fully visible in tracefs. Move the field destruction after the call removal, and splice the field list back onto the event when the removal fails so the event remains in a consistent state.
- Products
- Kernel
- Affected versions
- Not specified
- Fixed versions
- 6.1.191, 6.12.111, 6.18.53, 6.6.158, 7.2.7
- CVEs
- CVE-2026-97924
- Confirmed fixed CVEs
- Not specified
- Updated in this feed
- 6 Nov 2026, 00:25 UTC · Revision 1
Source evidence
tracing/user_events: Don't destroy fields when event removal fails
core-osv · Original sourcePublished 25 Sept 2026, 10:22 UTC
In the Linux kernel, the following vulnerability has been resolved: tracing/user_events: Don't destroy fields when event removal fails destroy_user_event() destroys the event's fields before attempting to remove the trace event call. If user_event_set_call_visible() fails, e.g. because the event is still enabled and trace_remove_event_call() returns -EBUSY, the event is left registered with an irreversibly destroyed field list. Any subsequent interaction with the event then operates on an empty field list while it is still fully visible in tracefs. Move the field destruction after the call removal, and splice the field list back onto the event when the removal fails so the event remains in a consistent state.
osv:CVE-2026-97924
Kernel
Fixed versions: 6.1.191, 6.6.158, 6.12.111, 6.18.53, 7.2.7
Complete source record
{
"id": "c00fa5e628b97bdbc565241c27a3e3d6afeb65d358c945af1b6c9c20072cb2f4",
"url": "https://osv.dev/vulnerability/CVE-2026-97924",
"method": "structured",
"payload": {
"kind": "advisory",
"title": "tracing/user_events: Don't destroy fields when event removal fails",
"summary": "In the Linux kernel, the following vulnerability has been resolved: tracing/user_events: Don't destroy fields when event removal fails destroy_user_event() destroys the event's fields before attempting to remove the trace event call. If user_event_set_call_visible() fails, e.g. because the event is still enabled and trace_remove_event_call() returns -EBUSY, the event is left registered with an irreversibly destroyed field list. Any subsequent interaction with the event then operates on an empty field list while it is still fully visible in tracefs. Move the field destruction after the call removal, and splice the field list back onto the event when the removal fails so the event remains in a consistent state.",
"evidence": "osv:CVE-2026-97924",
"products": [
{
"name": {
"value": "Kernel",
"evidence": "/affected/1/package/name"
},
"prerequisites": [],
"fixed_versions": [
{
"value": "6.1.191",
"evidence": "/affected/1/ranges"
},
{
"value": "6.6.158",
"evidence": "/affected/1/ranges"
},
{
"value": "6.12.111",
"evidence": "/affected/1/ranges"
},
{
"value": "6.18.53",
"evidence": "/affected/1/ranges"
},
{
"value": "7.2.7",
"evidence": "/affected/1/ranges"
}
],
"affected_versions": []
}
],
"severity": "unknown",
"structured": {
"id": "CVE-2026-97924",
"aliases": [
"CVE-2026-97924"
],
"affected": [
{
"ranges": [
{
"repo": "https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git",
"type": "GIT",
"events": [
{
"introduced": "7f5a08c79df35e68f1a43033450c5050f12bc155"
},
{
"fixed": "c8efcb80f0b4d253482f9117db29bb92b4197d52"
},
{
"fixed": "a3d9b8b7c8f3627976fe758c77ffd3da260824d7"
},
{
"fixed": "9c62b7e92b6086a2a0aeb71f3553dd8cf7fdcd8b"
},
{
"fixed": "0892da2272ec565858aa1ec5458552d699de9142"
},
{
"fixed": "62d6544e86506bb0695c9594c713cba859666f2f"
},
{
"fixed": "2deb753127d7b7035e893955c5e91875e767d1f8"
}
]
}
],
"database_specific": {
"source": "https://storage.googleapis.com/cve-osv-conversion/osv-output/CVE-2026-97924.json"
}
},
{
"ranges": [
{
"type": "ECOSYSTEM",
"events": [
{
"introduced": "5.18.0"
},
{
"fixed": "6.1.191"
}
]
},
{
"type": "ECOSYSTEM",
"events": [
{
"introduced": "6.2.0"
},
{
"fixed": "6.6.158"
}
]
},
{
"type": "ECOSYSTEM",
"events": [
{
"introduced": "6.7.0"
},
{
"fixed": "6.12.111"
}
]
},
{
"type": "ECOSYSTEM",
"events": [
{
"introduced": "6.13.0"
},
{
"fixed": "6.18.53"
}
]
},
{
"type": "ECOSYSTEM",
"events": [
{
"introduced": "6.19.0"
},
{
"fixed": "7.2.7"
}
]
}
],
"package": {
"name": "Kernel",
"ecosystem": "Linux"
},
"database_specific": {
"source": "https://storage.googleapis.com/cve-osv-conversion/osv-output/CVE-2026-97924.json"
}
}
],
"modified": "2026-11-01T02:30:29.260340487Z",
"provider": "osv",
"references": [
"https://git.kernel.org/stable/c/0892da2272ec565858aa1ec5458552d699de9142",
"https://git.kernel.org/stable/c/2deb753127d7b7035e893955c5e91875e767d1f8",
"https://git.kernel.org/stable/c/62d6544e86506bb0695c9594c713cba859666f2f",
"https://git.kernel.org/stable/c/9c62b7e92b6086a2a0aeb71f3553dd8cf7fdcd8b",
"https://git.kernel.org/stable/c/a3d9b8b7c8f3627976fe758c77ffd3da260824d7",
"https://git.kernel.org/stable/c/c8efcb80f0b4d253482f9117db29bb92b4197d52",
"https://github.com/CVEProject/cvelistV5/tree/main/cves/2026/97xxx/CVE-2026-97924.json",
"https://nvd.nist.gov/vuln/detail/CVE-2026-97924",
"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/2026/97xxx/CVE-2026-97924.json"
}
},
"related_cves": [
{
"value": "CVE-2026-97924",
"evidence": "/id"
}
],
"security_relevant": true,
"severity_evidence": null
},
"source_id": "core-osv",
"document_id": 513465,
"published_at": "2026-09-25T10:22:42.935+00:00"
}