CVE-2026-45891net: hns3: fix double free issue for tx spare buffer
- 7.8HighCVSS base score
- 0.13%Exploitation in 30 daysEPSS · top 97% of all CVEs
- NoKnown exploitednot in CISA's KEV catalog
- NonePublic exploitsnone known yet
Description
In the Linux kernel, the following vulnerability has been resolved: net: hns3: fix double free issue for tx spare buffer In hns3_set_ringparam(), a temporary copy (tmp_rings) of the ring structure is created for rollback. However, the tx_spare pointer in the original ring handle is incorrectly left pointing to the old backup memory. Later, if memory allocation fails in hns3_init_all_ring() during the setup, the error path attempts to free all newly allocated rings. Since tx_spare contains a stale (non-NULL) pointer from the backup, it is mistaken for a newly allocated buffer and is erroneously freed, leading to a double-free of the backup memory. The root cause is that the tx_spare field was not cleared after its value was saved in tmp_rings, leaving a dangling pointer. Fix this by setting tx_spare to NULL in the original ring structure when the creation of the new `tx_spare` fails. This ensures the error cleanup path only frees genuinely newly allocated buffers.
Timeline
ID reserved
By Linux
- 14 days later
· 14 days later
Published
- 5 months later
· 5 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
| Scored by | CVSS | Score | Vector |
|---|---|---|---|
| NVDNVD · Analyzed | 3.1 | High7.8 | CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H |
- EPSS (exploitation in 30 days)
- 0.13% · top 97% of all CVEs (17 Nov 2026)
- CISA SSVC
- Exploitation: none · Automatable: no · Technical impact: partial
The list uses the assigner's score when there is one, then CISA's, then NVD's: High 7.8.
Affected products
- affected 907676b130711fd1f627824559e92259db2061d1 – < fb6a4c376d454b425555b1b0bda36e99f56ec307
- affected 907676b130711fd1f627824559e92259db2061d1 – < 43015461662d41dcfb3bb95fadd8a2a42ad8eacf
- affected 907676b130711fd1f627824559e92259db2061d1 – < 6dc10494cfe27b6f1e9adb7e293293ae39c50b7c
- affected 907676b130711fd1f627824559e92259db2061d1 – < d2c785733dfb853ea0b53984c75662a1af230a94
- affected 907676b130711fd1f627824559e92259db2061d1 – < fdbccddb7e7822016601829f95de4008e193f7bc
- affected 907676b130711fd1f627824559e92259db2061d1 – < c3659273860bed0c8e573b865e3769abc51225a8
- affected 907676b130711fd1f627824559e92259db2061d1 – < 6d2f142b1e4b203387a92519d9d2e34752a79dbb
- affected 5.14
- unaffected < 5.14
- unaffected 5.15.202 – ≤ 5.15.*
- unaffected 6.1.165 – ≤ 6.1.*
- unaffected 6.6.128 – ≤ 6.6.*
- unaffected 6.12.75 – ≤ 6.12.*
- unaffected 6.18.14 – ≤ 6.18.*
- unaffected 6.19.4 – ≤ 6.19.*
- unaffected 7.0 – ≤ *
References
References7
- https://git.kernel.org/stable/c/fb6a4c376d454b425555b1b0bda36e99f56ec307 (opens in a new tab)
- https://git.kernel.org/stable/c/43015461662d41dcfb3bb95fadd8a2a42ad8eacf (opens in a new tab)
- https://git.kernel.org/stable/c/6dc10494cfe27b6f1e9adb7e293293ae39c50b7c (opens in a new tab)
- https://git.kernel.org/stable/c/d2c785733dfb853ea0b53984c75662a1af230a94 (opens in a new tab)
- https://git.kernel.org/stable/c/fdbccddb7e7822016601829f95de4008e193f7bc (opens in a new tab)
- https://git.kernel.org/stable/c/c3659273860bed0c8e573b865e3769abc51225a8 (opens in a new tab)
- https://git.kernel.org/stable/c/6d2f142b1e4b203387a92519d9d2e34752a79dbb (opens in a new tab)
Sources
The same CVE in the primary databases and aggregators, to check against.
- CVE.org record (opens in a new tab)
- CVE List JSON (GitHub) (opens in a new tab)
- NVD (opens in a new tab)
- FIRST EPSS (opens in a new tab)
- EUVD EUVD-2026-32357 (opens in a new tab)
- OSV.dev (opens in a new tab)
- GitHub Advisories (opens in a new tab)
- CIRCL Vulnerability-Lookup (opens in a new tab)
Badge for a README or a ticket
[](https://cveledger.app/cve/CVE-2026-45891)Record last updated .