Skip to content
CVE Ledger
  • Newest CVEsPage
  • Recently added to KEVPage
  • Rising exploitation (EPSS)Page
  • Weekly digestPage
  • StatisticsPage
  • WatchlistPage
  • API docsPage
  • MCP serverPage
  • AboutPage
  • Data sourcesPage
  • Data statusPage
  • ChangelogPage
  • How it's builtPage
  • Support the projectPage

14 results

Back

CVE-2026-63922ipv6: exthdrs: refresh nh after handling HAO option

Description

In the Linux kernel, the following vulnerability has been resolved: ipv6: exthdrs: refresh nh after handling HAO option ip6_parse_tlv() caches skb_network_header(skb) in nh while walking IPv6 TLVs. ipv6_dest_hao() may call pskb_expand_head() for a cloned skb, which can move the skb head and invalidate the cached network header pointer. Refresh nh after ipv6_dest_hao() returns so any trailing padding or TLVs are parsed from the current skb head. This matches the existing pattern used in ip6_parse_tlv() after helpers that can modify skb header storage.

Timeline

  1. ID reserved

    By Linux

  2. Published

  3. · 3 months later

    Record updated

Changes after publication (a new score, a public exploit, EPSS crossing 1, 10 or 50 %, leaving KEV) are kept since November 2026; earlier ones are not known.

Scores

CVSS scores of CVE-2026-63922, by who scored it
Scored byCVSSScoreVector
LinuxCNA (assigner)3.1Critical9.8CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
NVDNVD · Analyzed3.1Critical9.8CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
EPSS (exploitation in 30 days)
0.71% · top 45% of all CVEs (22 Nov 2026)
CISA SSVC
Exploitation: none · Automatable: yes · Technical impact: total
Loading the EPSS history…

The list uses the assigner's score when there is one, then CISA's, then NVD's: Critical 9.8.

Affected products

  • Linux · Linux

    • affected a831f5bbc89a9978795504be9e1ff412043f8f77 – < b3ac54e5c905f86d22b502eacb5686a282c5659f
    • affected a831f5bbc89a9978795504be9e1ff412043f8f77 – < f8aabed3ff3e986920cf02a2a2785e08e586b234
    • affected a831f5bbc89a9978795504be9e1ff412043f8f77 – < 1a11eb7431e3d2882f5bd5939c5a9bbc65ccf4d1
    • affected a831f5bbc89a9978795504be9e1ff412043f8f77 – < 12d957979e4a800167842f1b42be6a606d227ebe
    • affected a831f5bbc89a9978795504be9e1ff412043f8f77 – < ff375ed1cba81392346c5bfbf0bb7a13b2946f99
    • affected a831f5bbc89a9978795504be9e1ff412043f8f77 – < 751db1b802a067b7fff25880f4e9f9152a171538
    • affected a831f5bbc89a9978795504be9e1ff412043f8f77 – < 9b6dcc0a39fd71752937f0b6b3973e1416085dcf
    • affected a831f5bbc89a9978795504be9e1ff412043f8f77 – < f7b52afe3592eae66e160586b45a3f2242972c63
  • Linux · Linux

    • affected 2.6.19
    • unaffected < 2.6.19
    • unaffected 5.10.259 – ≤ 5.10.*
    • unaffected 5.15.210 – ≤ 5.15.*
    • unaffected 6.1.176 – ≤ 6.1.*
    • unaffected 6.6.143 – ≤ 6.6.*
    • unaffected 6.12.93 – ≤ 6.12.*
    • unaffected 6.18.35 – ≤ 6.18.*
    • unaffected 7.0.12 – ≤ 7.0.*
    • unaffected 7.1 – ≤ *

References

References8

Sources

The same CVE in the primary databases and aggregators, to check against.

Badge for a README or a ticket

CVE-2026-63922 badge
[![CVE-2026-63922](https://cveledger.app/badge/CVE-2026-63922.svg)](https://cveledger.app/cve/CVE-2026-63922)

Record last updated .