CVE-2026-23413 (GCVE-0-2026-23413)
Vulnerability from cvelistv5 – Published: 2026-04-02 11:40 – Updated: 2026-04-13 06:06
VLAI?
Title
clsact: Fix use-after-free in init/destroy rollback asymmetry
Summary
In the Linux kernel, the following vulnerability has been resolved:
clsact: Fix use-after-free in init/destroy rollback asymmetry
Fix a use-after-free in the clsact qdisc upon init/destroy rollback asymmetry.
The latter is achieved by first fully initializing a clsact instance, and
then in a second step having a replacement failure for the new clsact qdisc
instance. clsact_init() initializes ingress first and then takes care of the
egress part. This can fail midway, for example, via tcf_block_get_ext(). Upon
failure, the kernel will trigger the clsact_destroy() callback.
Commit 1cb6f0bae504 ("bpf: Fix too early release of tcx_entry") details the
way how the transition is happening. If tcf_block_get_ext on the q->ingress_block
ends up failing, we took the tcx_miniq_inc reference count on the ingress
side, but not yet on the egress side. clsact_destroy() tests whether the
{ingress,egress}_entry was non-NULL. However, even in midway failure on the
replacement, both are in fact non-NULL with a valid egress_entry from the
previous clsact instance.
What we really need to test for is whether the qdisc instance-specific ingress
or egress side previously got initialized. This adds a small helper for checking
the miniq initialization called mini_qdisc_pair_inited, and utilizes that upon
clsact_destroy() in order to fix the use-after-free scenario. Convert the
ingress_destroy() side as well so both are consistent to each other.
Severity ?
No CVSS data available.
Assigner
References
Impacted products
| Vendor | Product | Version | ||
|---|---|---|---|---|
| Linux | Linux |
Affected:
230bb13650b0f186f540500fd5f5f7096a822a2a , < a73d95b57bf9faebdfed591bcb7ed9292062a84c
(git)
Affected: 1cb6f0bae50441f4b4b32a28315853b279c7404e , < 37bef86e5428d59f70a4da82b80f9a8f252fecbe (git) Affected: 1cb6f0bae50441f4b4b32a28315853b279c7404e , < 4c9af67f99aa3e51b522c54968ab3ac8272be41c (git) Affected: 1cb6f0bae50441f4b4b32a28315853b279c7404e , < 0509b762bc5e8ea7b8391130730c6d8502fc6e69 (git) Affected: 1cb6f0bae50441f4b4b32a28315853b279c7404e , < a0671125d4f55e1e98d9bde8a0b671941987e208 (git) Affected: f61ecf1bd5b562ebfd7d430ccb31619857e80857 (git) |
||
{
"containers": {
"cna": {
"affected": [
{
"defaultStatus": "unaffected",
"product": "Linux",
"programFiles": [
"include/net/sch_generic.h",
"net/sched/sch_ingress.c"
],
"repo": "https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git",
"vendor": "Linux",
"versions": [
{
"lessThan": "a73d95b57bf9faebdfed591bcb7ed9292062a84c",
"status": "affected",
"version": "230bb13650b0f186f540500fd5f5f7096a822a2a",
"versionType": "git"
},
{
"lessThan": "37bef86e5428d59f70a4da82b80f9a8f252fecbe",
"status": "affected",
"version": "1cb6f0bae50441f4b4b32a28315853b279c7404e",
"versionType": "git"
},
{
"lessThan": "4c9af67f99aa3e51b522c54968ab3ac8272be41c",
"status": "affected",
"version": "1cb6f0bae50441f4b4b32a28315853b279c7404e",
"versionType": "git"
},
{
"lessThan": "0509b762bc5e8ea7b8391130730c6d8502fc6e69",
"status": "affected",
"version": "1cb6f0bae50441f4b4b32a28315853b279c7404e",
"versionType": "git"
},
{
"lessThan": "a0671125d4f55e1e98d9bde8a0b671941987e208",
"status": "affected",
"version": "1cb6f0bae50441f4b4b32a28315853b279c7404e",
"versionType": "git"
},
{
"status": "affected",
"version": "f61ecf1bd5b562ebfd7d430ccb31619857e80857",
"versionType": "git"
}
]
},
{
"defaultStatus": "affected",
"product": "Linux",
"programFiles": [
"include/net/sch_generic.h",
"net/sched/sch_ingress.c"
],
"repo": "https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git",
"vendor": "Linux",
"versions": [
{
"status": "affected",
"version": "6.10"
},
{
"lessThan": "6.10",
"status": "unaffected",
"version": "0",
"versionType": "semver"
},
{
"lessThanOrEqual": "6.6.*",
"status": "unaffected",
"version": "6.6.130",
"versionType": "semver"
},
{
"lessThanOrEqual": "6.12.*",
"status": "unaffected",
"version": "6.12.78",
"versionType": "semver"
},
{
"lessThanOrEqual": "6.18.*",
"status": "unaffected",
"version": "6.18.20",
"versionType": "semver"
},
{
"lessThanOrEqual": "6.19.*",
"status": "unaffected",
"version": "6.19.10",
"versionType": "semver"
},
{
"lessThanOrEqual": "*",
"status": "unaffected",
"version": "7.0",
"versionType": "original_commit_for_fix"
}
]
}
],
"cpeApplicability": [
{
"nodes": [
{
"cpeMatch": [
{
"criteria": "cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*",
"versionEndExcluding": "6.6.130",
"versionStartIncluding": "6.6.41",
"vulnerable": true
},
{
"criteria": "cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*",
"versionEndExcluding": "6.12.78",
"versionStartIncluding": "6.10",
"vulnerable": true
},
{
"criteria": "cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*",
"versionEndExcluding": "6.18.20",
"versionStartIncluding": "6.10",
"vulnerable": true
},
{
"criteria": "cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*",
"versionEndExcluding": "6.19.10",
"versionStartIncluding": "6.10",
"vulnerable": true
},
{
"criteria": "cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*",
"versionEndExcluding": "7.0",
"versionStartIncluding": "6.10",
"vulnerable": true
},
{
"criteria": "cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*",
"versionStartIncluding": "6.9.10",
"vulnerable": true
}
],
"negate": false,
"operator": "OR"
}
]
}
],
"descriptions": [
{
"lang": "en",
"value": "In the Linux kernel, the following vulnerability has been resolved:\n\nclsact: Fix use-after-free in init/destroy rollback asymmetry\n\nFix a use-after-free in the clsact qdisc upon init/destroy rollback asymmetry.\nThe latter is achieved by first fully initializing a clsact instance, and\nthen in a second step having a replacement failure for the new clsact qdisc\ninstance. clsact_init() initializes ingress first and then takes care of the\negress part. This can fail midway, for example, via tcf_block_get_ext(). Upon\nfailure, the kernel will trigger the clsact_destroy() callback.\n\nCommit 1cb6f0bae504 (\"bpf: Fix too early release of tcx_entry\") details the\nway how the transition is happening. If tcf_block_get_ext on the q-\u003eingress_block\nends up failing, we took the tcx_miniq_inc reference count on the ingress\nside, but not yet on the egress side. clsact_destroy() tests whether the\n{ingress,egress}_entry was non-NULL. However, even in midway failure on the\nreplacement, both are in fact non-NULL with a valid egress_entry from the\nprevious clsact instance.\n\nWhat we really need to test for is whether the qdisc instance-specific ingress\nor egress side previously got initialized. This adds a small helper for checking\nthe miniq initialization called mini_qdisc_pair_inited, and utilizes that upon\nclsact_destroy() in order to fix the use-after-free scenario. Convert the\ningress_destroy() side as well so both are consistent to each other."
}
],
"providerMetadata": {
"dateUpdated": "2026-04-13T06:06:57.208Z",
"orgId": "416baaa9-dc9f-4396-8d5f-8c081fb06d67",
"shortName": "Linux"
},
"references": [
{
"url": "https://git.kernel.org/stable/c/a73d95b57bf9faebdfed591bcb7ed9292062a84c"
},
{
"url": "https://git.kernel.org/stable/c/37bef86e5428d59f70a4da82b80f9a8f252fecbe"
},
{
"url": "https://git.kernel.org/stable/c/4c9af67f99aa3e51b522c54968ab3ac8272be41c"
},
{
"url": "https://git.kernel.org/stable/c/0509b762bc5e8ea7b8391130730c6d8502fc6e69"
},
{
"url": "https://git.kernel.org/stable/c/a0671125d4f55e1e98d9bde8a0b671941987e208"
}
],
"title": "clsact: Fix use-after-free in init/destroy rollback asymmetry",
"x_generator": {
"engine": "bippy-1.2.0"
}
}
},
"cveMetadata": {
"assignerOrgId": "416baaa9-dc9f-4396-8d5f-8c081fb06d67",
"assignerShortName": "Linux",
"cveId": "CVE-2026-23413",
"datePublished": "2026-04-02T11:40:54.384Z",
"dateReserved": "2026-01-13T15:37:46.014Z",
"dateUpdated": "2026-04-13T06:06:57.208Z",
"state": "PUBLISHED"
},
"dataType": "CVE_RECORD",
"dataVersion": "5.2",
"vulnerability-lookup:meta": {
"epss": {
"cve": "CVE-2026-23413",
"date": "2026-04-14",
"epss": "0.00024",
"percentile": "0.06307"
},
"nvd": "{\"cve\":{\"id\":\"CVE-2026-23413\",\"sourceIdentifier\":\"416baaa9-dc9f-4396-8d5f-8c081fb06d67\",\"published\":\"2026-04-02T12:16:20.440\",\"lastModified\":\"2026-04-03T16:10:52.680\",\"vulnStatus\":\"Awaiting Analysis\",\"cveTags\":[],\"descriptions\":[{\"lang\":\"en\",\"value\":\"In the Linux kernel, the following vulnerability has been resolved:\\n\\nclsact: Fix use-after-free in init/destroy rollback asymmetry\\n\\nFix a use-after-free in the clsact qdisc upon init/destroy rollback asymmetry.\\nThe latter is achieved by first fully initializing a clsact instance, and\\nthen in a second step having a replacement failure for the new clsact qdisc\\ninstance. clsact_init() initializes ingress first and then takes care of the\\negress part. This can fail midway, for example, via tcf_block_get_ext(). Upon\\nfailure, the kernel will trigger the clsact_destroy() callback.\\n\\nCommit 1cb6f0bae504 (\\\"bpf: Fix too early release of tcx_entry\\\") details the\\nway how the transition is happening. If tcf_block_get_ext on the q-\u003eingress_block\\nends up failing, we took the tcx_miniq_inc reference count on the ingress\\nside, but not yet on the egress side. clsact_destroy() tests whether the\\n{ingress,egress}_entry was non-NULL. However, even in midway failure on the\\nreplacement, both are in fact non-NULL with a valid egress_entry from the\\nprevious clsact instance.\\n\\nWhat we really need to test for is whether the qdisc instance-specific ingress\\nor egress side previously got initialized. This adds a small helper for checking\\nthe miniq initialization called mini_qdisc_pair_inited, and utilizes that upon\\nclsact_destroy() in order to fix the use-after-free scenario. Convert the\\ningress_destroy() side as well so both are consistent to each other.\"}],\"metrics\":{},\"references\":[{\"url\":\"https://git.kernel.org/stable/c/0509b762bc5e8ea7b8391130730c6d8502fc6e69\",\"source\":\"416baaa9-dc9f-4396-8d5f-8c081fb06d67\"},{\"url\":\"https://git.kernel.org/stable/c/37bef86e5428d59f70a4da82b80f9a8f252fecbe\",\"source\":\"416baaa9-dc9f-4396-8d5f-8c081fb06d67\"},{\"url\":\"https://git.kernel.org/stable/c/4c9af67f99aa3e51b522c54968ab3ac8272be41c\",\"source\":\"416baaa9-dc9f-4396-8d5f-8c081fb06d67\"},{\"url\":\"https://git.kernel.org/stable/c/a0671125d4f55e1e98d9bde8a0b671941987e208\",\"source\":\"416baaa9-dc9f-4396-8d5f-8c081fb06d67\"},{\"url\":\"https://git.kernel.org/stable/c/a73d95b57bf9faebdfed591bcb7ed9292062a84c\",\"source\":\"416baaa9-dc9f-4396-8d5f-8c081fb06d67\"}]}}"
}
}
Loading…
Loading…
Sightings
| Author | Source | Type | Date |
|---|
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.
Loading…
Loading…