7.5

CVE-2026-68120: linux

CVSS: 7.5v3.1HighReceived
AliasesUBUNTU-CVE-2026-68120DEBIAN-CVE-2026-68120
Published 10-08-2026Last modified 17-08-2026

Vulnerability summary

CVE-2026-68120 is a high (CVSS 7.5) vulnerability in linux. EPSS estimates a 0.44% chance of exploitation in the next 30 days, higher than 36.9% of scored vulnerabilities.

Overall risk
30/100
0100
Medium · default modelHow is this calculated?
CVSS score
7.5/10
010
High · v3.1 (CVE.org)
EPSS score
0.44%
0%100%
Low · 0.00 pp in 30 days
KEVNot listedIn no KEV catalog
RansomwareNone recordedNo known use recorded
Public exploits0No public exploits recorded

Advisory lineage

Upstream 0 · Downstream 13 · Related 11

Timeline

  1. 10-08-2026
    PublishedVulnerability first disclosed.
  2. 17-08-2026
    Last modifiedVulnerability information updated.

Description

In the Linux kernel, the following vulnerability has been resolved: rtase: Workaround for TX hang caused by hardware packet parsing The hardware performs packet parsing before packet transmission. Parsing incomplete IPv4, IPv6, TCP, or UDP headers may trigger a TX hang because the hardware parser expects additional protocol header data that is not present in the packet. The hardware performs additional PTP parsing on UDP packets identified by destination ports 319/320 at the expected UDP destination port offset. If such a packet has transport data smaller than RTASE_MIN_PAD_LEN, the hardware parser expects additional packet data and may trigger a TX hang. To avoid these hardware issues, the driver applies the following workarounds. Drop malformed packets that may trigger this hardware issue before transmission. For IPv4 non-initial fragments, the hardware does not check the fragment offset before parsing the expected transport header location. As a result, these packets are still subject to transport header parsing even though they do not contain a transport header. If the transport data is shorter than the minimum transport header required by the hardware parser, pad the transport data to the minimum transport header length required by the hardware parser. Packets that also match the hardware PTP parsing conditions continue to follow the corresponding workaround. For IPv6 fragmented packets, neither of the above hardware issues occurs because the hardware only continues packet parsing when the IPv6 Base Header Next Header field directly indicates UDP. Packets carrying a Fragment Header do not continue through the subsequent packet parsing stages. For packets identified for hardware PTP parsing, pad the transport data so it reaches RTASE_MIN_PAD_LEN before transmission.

CVSS metrics

4 scores · 4 sources · 1 version

EPSS trend

Probability

0.44%

Chance of exploitation in the next 30 days

Percentile

37%

Versus all other CVEs

30-day change

0.00 pp

From 0.44% on 19-09-2026

19-09-202619-10-2026
EPSS score
0.44%

Known exploited

Compare KEV catalogs

Not in any of the 3 tracked catalogs.

Public exploits

0 found

No public exploits indexed.

Weaknesses

CWE · root cause

No weakness data has been published for this record.

Affected systems

Ubuntu120 products
  • linux< 7.0.0-38.38
  • linux-allwinner-5.19All versions (No fix recorded)
  • linux-aws< 7.0.0-1014.14
  • linux-aws-5.0All versions (No fix recorded)
  • linux-aws-5.11All versions (No fix recorded)
Debian2 products
  • linux< 6.12.101-1 | < 7.1.6-1
  • linux-6.12< 6.12.101-1~deb12u1
Linux1 product
  • linux≥ d6e882b89fdf80be0ab4f914ec10f75215e49495, < fe3a7320711eec6537e4890892f7ab9776d8618f | ≥ d6e882b89fdf80be0ab4f914ec10f75215e49495, < 4a4f3aa6af205bee539b5670afa2cd4e4953750e | ≥ d6e882b89fdf80be0ab4f914ec10f75215e49495, < 0f54f5048615e4e2802697855ea6374613548301 | ≥ d6e882b89fdf80be0ab4f914ec10f75215e49495, < 1c50efa1faf3a1a96e100b07ec7a2f3164d90bee | 6.12

3 vendors · 123 products

References

13 links
Show all 13 references