Answer in brief
CVE-2026-72429 records a Critical severity (CVSS 9.8) vulnerability in ipv6: ioam: fix type confusion of dst_entry. The current sources do not mark it as known exploited. The current feed maps Linux/Linux (generic), Linux/Linux (generic). Check affected ranges and fixed versions before updating.
Analysis pending evidence review
HOL Guard separates source facts from reviewed analysis. See the methodology.
CVSS is 9.8. The current sources do not mark it as known exploited. Treat this as a source-backed prioritization signal, not a statement about your environment.
Analysis status
Analysis pending evidence review
Factual feed record only; HOL analysis is not approved for indexing. Read the methodology.
The current feed maps Linux/Linux (generic), Linux/Linux (generic). Check affected ranges and fixed versions before updating.
| Package | Affected range | Fixed version |
|---|---|---|
| Linux/Linuxgeneric | >=47ce7c854563fe8450e9cb8dcd62c6470e28076b <ea24f911ead85ba3d570a31e37c52b6c949f6928 || >=47ce7c854563fe8450e9cb8dcd62c6470e28076b <5a3b2ee1e96d0580a8ed8deda6dfa430604f9ab0 || >=47ce7c854563fe8450e9cb8dcd62c6470e28076b <9ed19e11d2146076d117d51a940643990118449b | ea24f911ead85ba3d570a31e37c52b6c949f6928, 5a3b2ee1e96d0580a8ed8deda6dfa430604f9ab0, 9ed19e11d2146076d117d51a940643990118449b |
| Linux/Linuxgeneric | 6.16 | Not reported |
Published upstream
Aug 15, 2026
Evidence: source:cvelist:source_dates:source-dates:recordSource modified
Aug 17, 2026
Evidence: source:cvelist:source_dates:source-dates:recordFirst seen by HOL
Aug 15, 2026
In the Linux kernel, the following vulnerability has been resolved: ipv6: ioam: fix type confusion of dst_entry IOAM uses a dummy dst_entry(null_dst) to mark that the destination should not be changed after the transformation. This dst is stored in the IOAM lwt state and may be passed to dst_cache_set_ip6(). However, the IPv6 dst cache path eventually calls rt6_get_cookie(), which treats the dst_entry as part of a struct rt6_info. Since the null_dst was embedded directly as a struct dst_entry in struct ioam6_lwt, this resulted in an invalid cast and rt6_get_cookie() reading fields from the wrong object. In practice, the wrong cookie is not used while dst->obsolete is zero, but rt6_get_cookie() may also access per-cpu value when rt->sernum is zero. In this case, rt->sernum aliases ioam6_lwt::cache::reset_ts, which can become zero, making this a potential invalid pointer access. Fix this by embedding a full struct rt6_info for the dummy IPv6 route and passing its dst member to the dst APIs.
Quoted source text, attributed separately from HOL analysis.