FKIE_CVE-2026-98598
Vulnerability from fkie_nvd - Published: 2026-10-18 16:17 - Updated: 2026-10-19 10:19
Severity
Summary
In the Linux kernel, the following vulnerability has been resolved:
ipv6: Prevent rt6_insert_exception() for dying fib6_info.
Before the cited commit, fib6_nh_flush_exceptions() always set
from->exception_bucket_flushed = 1 under rt6_exception_lock to
prevent rt6_insert_exception() from inserting a new exception
for a dying fib6_info.
The flag was replaced with the FIB6_EXCEPTION_BUCKET_FLUSHED
bit stored in nh->rt6i_exception_bucket.
The problem is that now the bit is only set when the bucket
is not NULL and fib6_nh_flush_exceptions() is called from
fib6_nh_release() after fib6_ref has already reached zero.
If rt6_insert_exception() is called while the target fib6_info
is being removed via fib6_purge_rt(), a new exception could be
created successfully because rt6_flush_exceptions() no longer
sets the bit.
This creates a reference cycle between the fib6_info and the
exception route, leaking the fib6_info, its nexthop device,
and all per-CPU routes in fib6_nh->rt6i_pcpu, which stalls netdev
unregistration.
[ 34.680602] unregister_netdevice: waiting for gre6 to become free. Usage count = 68
[ 44.920675] unregister_netdevice: waiting for gre6 to become free. Usage count = 68
[ 55.176582] unregister_netdevice: waiting for gre6 to become free. Usage count = 68
Let's call fib6_drop_pcpu_from() before rt6_flush_exceptions(),
to set fib6_destroying before rt6_exception_lock, and check
f6i->fib6_destroying in rt6_insert_exception().
Note that FIB6_EXCEPTION_BUCKET_FLUSHED logic is dead and
we can clean it up in net-next.
References
Impacted products
| Vendor | Product | Version |
|---|
{
"affected": [
{
"affectedData": [
{
"defaultStatus": "unaffected",
"product": "Linux",
"programFiles": [
"net/ipv6/ip6_fib.c",
"net/ipv6/route.c"
],
"repo": "https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git",
"vendor": "Linux",
"versions": [
{
"lessThan": "649ffc76ed5483b2caf35ed90d3787538efc4e53",
"status": "affected",
"version": "cc5c073a693fa6ed7a207b0436114f68cce72434",
"versionType": "git"
},
{
"lessThan": "e03e77071e75ce726d877f0a4349a28b6e1f487a",
"status": "affected",
"version": "cc5c073a693fa6ed7a207b0436114f68cce72434",
"versionType": "git"
},
{
"lessThan": "0346ec2f080b40d95ed05b853bb9226289e75212",
"status": "affected",
"version": "cc5c073a693fa6ed7a207b0436114f68cce72434",
"versionType": "git"
}
]
},
{
"defaultStatus": "affected",
"product": "Linux",
"programFiles": [
"net/ipv6/ip6_fib.c",
"net/ipv6/route.c"
],
"repo": "https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git",
"vendor": "Linux",
"versions": [
{
"status": "affected",
"version": "5.3"
},
{
"lessThan": "5.3",
"status": "unaffected",
"version": "0",
"versionType": "semver"
},
{
"lessThanOrEqual": "6.18.*",
"status": "unaffected",
"version": "6.18.55",
"versionType": "semver"
},
{
"lessThanOrEqual": "7.2.*",
"status": "unaffected",
"version": "7.2.9",
"versionType": "semver"
},
{
"lessThanOrEqual": "*",
"status": "unaffected",
"version": "7.3",
"versionType": "original_commit_for_fix"
}
]
}
],
"source": "416baaa9-dc9f-4396-8d5f-8c081fb06d67"
}
],
"cveTags": [],
"descriptions": [
{
"lang": "en",
"value": "In the Linux kernel, the following vulnerability has been resolved:\n\nipv6: Prevent rt6_insert_exception() for dying fib6_info.\n\nBefore the cited commit, fib6_nh_flush_exceptions() always set\nfrom-\u003eexception_bucket_flushed = 1 under rt6_exception_lock to\nprevent rt6_insert_exception() from inserting a new exception\nfor a dying fib6_info.\n\nThe flag was replaced with the FIB6_EXCEPTION_BUCKET_FLUSHED\nbit stored in nh-\u003ert6i_exception_bucket.\n\nThe problem is that now the bit is only set when the bucket\nis not NULL and fib6_nh_flush_exceptions() is called from\nfib6_nh_release() after fib6_ref has already reached zero.\n\nIf rt6_insert_exception() is called while the target fib6_info\nis being removed via fib6_purge_rt(), a new exception could be\ncreated successfully because rt6_flush_exceptions() no longer\nsets the bit.\n\nThis creates a reference cycle between the fib6_info and the\nexception route, leaking the fib6_info, its nexthop device,\nand all per-CPU routes in fib6_nh-\u003ert6i_pcpu, which stalls netdev\nunregistration.\n\n[ 34.680602] unregister_netdevice: waiting for gre6 to become free. Usage count = 68\n[ 44.920675] unregister_netdevice: waiting for gre6 to become free. Usage count = 68\n[ 55.176582] unregister_netdevice: waiting for gre6 to become free. Usage count = 68\n\nLet\u0027s call fib6_drop_pcpu_from() before rt6_flush_exceptions(),\nto set fib6_destroying before rt6_exception_lock, and check\nf6i-\u003efib6_destroying in rt6_insert_exception().\n\nNote that FIB6_EXCEPTION_BUCKET_FLUSHED logic is dead and\nwe can clean it up in net-next."
}
],
"id": "CVE-2026-98598",
"lastModified": "2026-10-19T10:19:21.240",
"metrics": {},
"published": "2026-10-18T16:17:12.500",
"references": [
{
"source": "416baaa9-dc9f-4396-8d5f-8c081fb06d67",
"url": "https://git.kernel.org/stable/c/0346ec2f080b40d95ed05b853bb9226289e75212"
},
{
"source": "416baaa9-dc9f-4396-8d5f-8c081fb06d67",
"url": "https://git.kernel.org/stable/c/649ffc76ed5483b2caf35ed90d3787538efc4e53"
},
{
"source": "416baaa9-dc9f-4396-8d5f-8c081fb06d67",
"url": "https://git.kernel.org/stable/c/e03e77071e75ce726d877f0a4349a28b6e1f487a"
}
],
"sourceIdentifier": "416baaa9-dc9f-4396-8d5f-8c081fb06d67",
"vulnStatus": "Received"
}
Loading…
Loading…
Experimental. This forecast is provided for visualization only and may change without notice. Do not use it for operational decisions.
Forecast uses a logistic model when the trend is rising, or an exponential decay model when the trend is falling. Fitted via linearized least squares.
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.
Loading…
Loading…
The MITRE ATT&CK techniques below are AI-generated suggestions, inferred from the description of the
vulnerability by the CIRCL/vulnerability-attack-technique-classification-roberta-base
model, served locally by ML-Gateway.
They have not been verified by an analyst and are provided for guidance only.
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.
Browse all ATT&CK techniques and the vulnerabilities related to each.
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.
Browse all ATT&CK techniques and the vulnerabilities related to each.
Loading…
Related by attack behaviour
Vulnerabilities whose description is nearest to this one in the vector space of the CIRCL/vulnerability-attack-technique-biencoder model. This is a similarity search over the bi-encoder space (plain cosine), not a classification, and it has no measured accuracy.
Loading…