CVE-2026-68120 (GCVE-0-2026-68120)

Vulnerability from cvelistv5 – Published: 2026-08-10 11:58 – Updated: 2026-08-17 04:59
VLAI
Title
rtase: Workaround for TX hang caused by hardware packet parsing
Summary
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.
Severity
7.5 (High)
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H
Assigner
References
Impacted products
Vendor Product Version
Linux Linux Affected: d6e882b89fdf80be0ab4f914ec10f75215e49495 , < fe3a7320711eec6537e4890892f7ab9776d8618f (git)
Affected: d6e882b89fdf80be0ab4f914ec10f75215e49495 , < 4a4f3aa6af205bee539b5670afa2cd4e4953750e (git)
Affected: d6e882b89fdf80be0ab4f914ec10f75215e49495 , < 0f54f5048615e4e2802697855ea6374613548301 (git)
Affected: d6e882b89fdf80be0ab4f914ec10f75215e49495 , < 1c50efa1faf3a1a96e100b07ec7a2f3164d90bee (git)
Create a notification for this product.
Linux Linux Affected: 6.12
Unaffected: 0 , < 6.12 (semver)
Unaffected: 6.12.101 , ≤ 6.12.* (semver)
Unaffected: 6.18.42 , ≤ 6.18.* (semver)
Unaffected: 7.1.6 , ≤ 7.1.* (semver)
Unaffected: 7.2 , ≤ * (original_commit_for_fix)
Create a notification for this product.
Show details on NVD website
To clipboard 

{
  "containers": {
    "cna": {
      "affected": [
        {
          "defaultStatus": "unaffected",
          "product": "Linux",
          "programFiles": [
            "drivers/net/ethernet/realtek/rtase/rtase.h",
            "drivers/net/ethernet/realtek/rtase/rtase_main.c"
          ],
          "repo": "https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git",
          "vendor": "Linux",
          "versions": [
            {
              "lessThan": "fe3a7320711eec6537e4890892f7ab9776d8618f",
              "status": "affected",
              "version": "d6e882b89fdf80be0ab4f914ec10f75215e49495",
              "versionType": "git"
            },
            {
              "lessThan": "4a4f3aa6af205bee539b5670afa2cd4e4953750e",
              "status": "affected",
              "version": "d6e882b89fdf80be0ab4f914ec10f75215e49495",
              "versionType": "git"
            },
            {
              "lessThan": "0f54f5048615e4e2802697855ea6374613548301",
              "status": "affected",
              "version": "d6e882b89fdf80be0ab4f914ec10f75215e49495",
              "versionType": "git"
            },
            {
              "lessThan": "1c50efa1faf3a1a96e100b07ec7a2f3164d90bee",
              "status": "affected",
              "version": "d6e882b89fdf80be0ab4f914ec10f75215e49495",
              "versionType": "git"
            }
          ]
        },
        {
          "defaultStatus": "affected",
          "product": "Linux",
          "programFiles": [
            "drivers/net/ethernet/realtek/rtase/rtase.h",
            "drivers/net/ethernet/realtek/rtase/rtase_main.c"
          ],
          "repo": "https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git",
          "vendor": "Linux",
          "versions": [
            {
              "status": "affected",
              "version": "6.12"
            },
            {
              "lessThan": "6.12",
              "status": "unaffected",
              "version": "0",
              "versionType": "semver"
            },
            {
              "lessThanOrEqual": "6.12.*",
              "status": "unaffected",
              "version": "6.12.101",
              "versionType": "semver"
            },
            {
              "lessThanOrEqual": "6.18.*",
              "status": "unaffected",
              "version": "6.18.42",
              "versionType": "semver"
            },
            {
              "lessThanOrEqual": "7.1.*",
              "status": "unaffected",
              "version": "7.1.6",
              "versionType": "semver"
            },
            {
              "lessThanOrEqual": "*",
              "status": "unaffected",
              "version": "7.2",
              "versionType": "original_commit_for_fix"
            }
          ]
        }
      ],
      "cpeApplicability": [
        {
          "nodes": [
            {
              "cpeMatch": [
                {
                  "criteria": "cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*",
                  "versionEndExcluding": "6.12.101",
                  "versionStartIncluding": "6.12",
                  "vulnerable": true
                },
                {
                  "criteria": "cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*",
                  "versionEndExcluding": "6.18.42",
                  "versionStartIncluding": "6.12",
                  "vulnerable": true
                },
                {
                  "criteria": "cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*",
                  "versionEndExcluding": "7.1.6",
                  "versionStartIncluding": "6.12",
                  "vulnerable": true
                },
                {
                  "criteria": "cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*",
                  "versionEndExcluding": "7.2",
                  "versionStartIncluding": "6.12",
                  "vulnerable": true
                }
              ],
              "negate": false,
              "operator": "OR"
            }
          ]
        }
      ],
      "descriptions": [
        {
          "lang": "en",
          "value": "In the Linux kernel, the following vulnerability has been resolved:\n\nrtase: Workaround for TX hang caused by hardware packet parsing\n\nThe hardware performs packet parsing before packet transmission.\nParsing incomplete IPv4, IPv6, TCP, or UDP headers may trigger a TX\nhang because the hardware parser expects additional protocol header\ndata that is not present in the packet.\n\nThe hardware performs additional PTP parsing on UDP packets identified\nby destination ports 319/320 at the expected UDP destination port\noffset.\n\nIf such a packet has transport data smaller than RTASE_MIN_PAD_LEN,\nthe hardware parser expects additional packet data and may trigger a\nTX hang.\n\nTo avoid these hardware issues, the driver applies the following\nworkarounds.\n\nDrop malformed packets that may trigger this hardware issue before\ntransmission.\n\nFor IPv4 non-initial fragments, the hardware does not check the\nfragment offset before parsing the expected transport header location.\nAs a result, these packets are still subject to transport header\nparsing even though they do not contain a transport header. If the\ntransport data is shorter than the minimum transport header required\nby the hardware parser, pad the transport data to the minimum\ntransport header length required by the hardware parser. Packets that\nalso match the hardware PTP parsing conditions continue to follow the\ncorresponding workaround.\n\nFor IPv6 fragmented packets, neither of the above hardware issues\noccurs because the hardware only continues packet parsing when the\nIPv6 Base Header Next Header field directly indicates UDP. Packets\ncarrying a Fragment Header do not continue through the subsequent\npacket parsing stages.\n\nFor packets identified for hardware PTP parsing, pad the transport\ndata so it reaches RTASE_MIN_PAD_LEN before transmission."
        }
      ],
      "metrics": [
        {
          "cvssV3_1": {
            "baseScore": 7.5,
            "baseSeverity": "HIGH",
            "vectorString": "CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H",
            "version": "3.1"
          },
          "scenarios": [
            {
              "lang": "en",
              "value": "AV:N - The bug is in netdev TX; a remote attacker can send crafted IPv4 fragments or short PTP UDP (ports 319/320) that are forwarded/bridged out the rtase interface on automotive gateways and industrial routers, reaching rtase_start_xmit without local access.\nAC:L - Trigger packets have well-defined shapes (non-initial IPv4 frags with short payload, malformed L3/L4 headers, or PTP UDP under 47 bytes) and the attacker controls generation, timing, and retries; no race or rare layout is required on affected hardware.\nPR:N - Exploitation requires only the ability to inject network traffic that the host forwards or transmits via the rtase netdev; no target credentials, capabilities, or local shell access are needed on forwarding automotive/industrial gateways.\nUI:N - No victim interaction is required; the hang is triggered automatically when the kernel queues the crafted packet for transmission through the vulnerable NIC.\nS:U - Impact is confined to kernel/network availability on the host running the rtase driver; it does not cross VM, container, or IOMMU security boundaries.\nC:N - The failure mode is a hardware TX parser hang with no memory corruption, out-of-bounds access, use-after-free, or information disclosure primitive.\nI:N - The vulnerability does not modify arbitrary data or enable code execution; it only stalls transmission until the netdev watchdog resets the interface.\nA:H - Malformed TX packets can hang the NIC hardware transmit path, stopping egress and disrupting connectivity until rtase_tx_timeout invokes software reset; repeated injection enables sustained denial of service on safety-critical automotive networks."
            }
          ]
        }
      ],
      "providerMetadata": {
        "dateUpdated": "2026-08-17T04:59:10.871Z",
        "orgId": "416baaa9-dc9f-4396-8d5f-8c081fb06d67",
        "shortName": "Linux"
      },
      "references": [
        {
          "url": "https://git.kernel.org/stable/c/fe3a7320711eec6537e4890892f7ab9776d8618f"
        },
        {
          "url": "https://git.kernel.org/stable/c/4a4f3aa6af205bee539b5670afa2cd4e4953750e"
        },
        {
          "url": "https://git.kernel.org/stable/c/0f54f5048615e4e2802697855ea6374613548301"
        },
        {
          "url": "https://git.kernel.org/stable/c/1c50efa1faf3a1a96e100b07ec7a2f3164d90bee"
        }
      ],
      "title": "rtase: Workaround for TX hang caused by hardware packet parsing",
      "x_generator": {
        "engine": "bippy-1.2.0"
      }
    }
  },
  "cveMetadata": {
    "assignerOrgId": "416baaa9-dc9f-4396-8d5f-8c081fb06d67",
    "assignerShortName": "Linux",
    "cveId": "CVE-2026-68120",
    "datePublished": "2026-08-10T11:58:40.224Z",
    "dateReserved": "2026-07-30T09:28:09.369Z",
    "dateUpdated": "2026-08-17T04:59:10.871Z",
    "state": "PUBLISHED"
  },
  "dataType": "CVE_RECORD",
  "dataVersion": "5.2",
  "vulnerability-lookup:meta": {
    "epss": {
      "cve": "CVE-2026-68120",
      "date": "2026-10-02",
      "epss": "0.00441",
      "percentile": "0.36016"
    },
    "nvd": {
      "cve": {
        "affected": [
          {
            "affectedData": [
              {
                "defaultStatus": "unaffected",
                "product": "Linux",
                "programFiles": [
                  "drivers/net/ethernet/realtek/rtase/rtase.h",
                  "drivers/net/ethernet/realtek/rtase/rtase_main.c"
                ],
                "repo": "https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git",
                "vendor": "Linux",
                "versions": [
                  {
                    "lessThan": "fe3a7320711eec6537e4890892f7ab9776d8618f",
                    "status": "affected",
                    "version": "d6e882b89fdf80be0ab4f914ec10f75215e49495",
                    "versionType": "git"
                  },
                  {
                    "lessThan": "4a4f3aa6af205bee539b5670afa2cd4e4953750e",
                    "status": "affected",
                    "version": "d6e882b89fdf80be0ab4f914ec10f75215e49495",
                    "versionType": "git"
                  },
                  {
                    "lessThan": "0f54f5048615e4e2802697855ea6374613548301",
                    "status": "affected",
                    "version": "d6e882b89fdf80be0ab4f914ec10f75215e49495",
                    "versionType": "git"
                  },
                  {
                    "lessThan": "1c50efa1faf3a1a96e100b07ec7a2f3164d90bee",
                    "status": "affected",
                    "version": "d6e882b89fdf80be0ab4f914ec10f75215e49495",
                    "versionType": "git"
                  }
                ]
              },
              {
                "defaultStatus": "affected",
                "product": "Linux",
                "programFiles": [
                  "drivers/net/ethernet/realtek/rtase/rtase.h",
                  "drivers/net/ethernet/realtek/rtase/rtase_main.c"
                ],
                "repo": "https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git",
                "vendor": "Linux",
                "versions": [
                  {
                    "status": "affected",
                    "version": "6.12"
                  },
                  {
                    "lessThan": "6.12",
                    "status": "unaffected",
                    "version": "0",
                    "versionType": "semver"
                  },
                  {
                    "lessThanOrEqual": "6.12.*",
                    "status": "unaffected",
                    "version": "6.12.101",
                    "versionType": "semver"
                  },
                  {
                    "lessThanOrEqual": "6.18.*",
                    "status": "unaffected",
                    "version": "6.18.42",
                    "versionType": "semver"
                  },
                  {
                    "lessThanOrEqual": "7.1.*",
                    "status": "unaffected",
                    "version": "7.1.6",
                    "versionType": "semver"
                  },
                  {
                    "lessThanOrEqual": "*",
                    "status": "unaffected",
                    "version": "7.2",
                    "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\nrtase: Workaround for TX hang caused by hardware packet parsing\n\nThe hardware performs packet parsing before packet transmission.\nParsing incomplete IPv4, IPv6, TCP, or UDP headers may trigger a TX\nhang because the hardware parser expects additional protocol header\ndata that is not present in the packet.\n\nThe hardware performs additional PTP parsing on UDP packets identified\nby destination ports 319/320 at the expected UDP destination port\noffset.\n\nIf such a packet has transport data smaller than RTASE_MIN_PAD_LEN,\nthe hardware parser expects additional packet data and may trigger a\nTX hang.\n\nTo avoid these hardware issues, the driver applies the following\nworkarounds.\n\nDrop malformed packets that may trigger this hardware issue before\ntransmission.\n\nFor IPv4 non-initial fragments, the hardware does not check the\nfragment offset before parsing the expected transport header location.\nAs a result, these packets are still subject to transport header\nparsing even though they do not contain a transport header. If the\ntransport data is shorter than the minimum transport header required\nby the hardware parser, pad the transport data to the minimum\ntransport header length required by the hardware parser. Packets that\nalso match the hardware PTP parsing conditions continue to follow the\ncorresponding workaround.\n\nFor IPv6 fragmented packets, neither of the above hardware issues\noccurs because the hardware only continues packet parsing when the\nIPv6 Base Header Next Header field directly indicates UDP. Packets\ncarrying a Fragment Header do not continue through the subsequent\npacket parsing stages.\n\nFor packets identified for hardware PTP parsing, pad the transport\ndata so it reaches RTASE_MIN_PAD_LEN before transmission."
          }
        ],
        "id": "CVE-2026-68120",
        "lastModified": "2026-08-17T05:18:11.557",
        "metrics": {
          "cvssMetricV31": [
            {
              "cvssData": {
                "attackComplexity": "LOW",
                "attackVector": "NETWORK",
                "availabilityImpact": "HIGH",
                "baseScore": 7.5,
                "baseSeverity": "HIGH",
                "confidentialityImpact": "NONE",
                "integrityImpact": "NONE",
                "privilegesRequired": "NONE",
                "scope": "UNCHANGED",
                "userInteraction": "NONE",
                "vectorString": "CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H",
                "version": "3.1"
              },
              "exploitabilityScore": 3.9,
              "impactScore": 3.6,
              "source": "416baaa9-dc9f-4396-8d5f-8c081fb06d67",
              "type": "Secondary"
            }
          ]
        },
        "published": "2026-08-10T13:19:57.073",
        "references": [
          {
            "source": "416baaa9-dc9f-4396-8d5f-8c081fb06d67",
            "url": "https://git.kernel.org/stable/c/0f54f5048615e4e2802697855ea6374613548301"
          },
          {
            "source": "416baaa9-dc9f-4396-8d5f-8c081fb06d67",
            "url": "https://git.kernel.org/stable/c/1c50efa1faf3a1a96e100b07ec7a2f3164d90bee"
          },
          {
            "source": "416baaa9-dc9f-4396-8d5f-8c081fb06d67",
            "url": "https://git.kernel.org/stable/c/4a4f3aa6af205bee539b5670afa2cd4e4953750e"
          },
          {
            "source": "416baaa9-dc9f-4396-8d5f-8c081fb06d67",
            "url": "https://git.kernel.org/stable/c/fe3a7320711eec6537e4890892f7ab9776d8618f"
          }
        ],
        "sourceIdentifier": "416baaa9-dc9f-4396-8d5f-8c081fb06d67",
        "vulnStatus": "Received"
      }
    },
    "redhat_vex": {
      "aggregate_severity": "None",
      "current_release_date": "2026-08-11T15:34:09+00:00",
      "cve": "CVE-2026-68120",
      "id": "CVE-2026-68120",
      "initial_release_date": "2026-08-10T00:00:00+00:00",
      "product_status:known_not_affected": "274",
      "source": "Red Hat CSAF VEX",
      "status": "final",
      "title": "kernel: rtase: Workaround for TX hang caused by hardware packet parsing",
      "url": "https://security.access.redhat.com/data/csaf/v2/vex/2026/cve-2026-68120.json",
      "version": "3"
    }
  }
}



Log in or create an account to share your comment.




Tags
Taxonomy of the tags.





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.



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.