In the Linux kernel, the following vulnerability has been resolved: net: ethernet: oa_tc6:...

zetlyn/cve-ghsa vulnerability ghsa GHSA-f226-mgwm-5x89 cve CVE-2026-98105 known 2026-09-25

https://github.com/advisories/GHSA-f226-mgwm-5x89

Properties

severityunknown
receipt
Source
GitHub advisories
Its words
unknown
Read by
field:severity
Said since
2026-09-28 11:44 UTC
Last answered
2026-10-06 13:46 UTC
Original
open at the source
What the source handed over
{
  "credits": [],
  "cve_id": "CVE-2026-98105",
  "cvss": {
    "score": null,
    "vector_string": null
  },
  "cvss_severities": {
    "cvss_v3": {
      "score": 0.0,
      "vector_string": null
    },
    "cvss_v4": {
      "score": 0.0,
      "vector_string": null
    }
  },
  "cwes": [],
  "description": "In the Linux kernel, the following vulnerability has been resolved:\n\nnet: ethernet: oa_tc6: Improve the error recovery\n\nWhen oversubscribed traffic causes lot of buffer overflow errors,\nprobably due to loss of data chunks, driver fails to find a\ndata chunk with end_valid bit set, before it runs out of sk buffer\nspace. As a result, assert is seen during skb_put.\n\nNow, check is made if skb buffer has enough tailroom for the\nincoming data before accepting. If there is no room, current\nframe is abandoned and it will start looking for a data chunk\nwith start_valid bit, that is a new frame.\n\nSK buffer allocation error is considered as recoverable error.\n\nrx_buf_overflow flag is too specific and no longer the only\ncondition this flag is used for. Therefore it is renamed as\nwait_until_start_valid. This is more appropriate as this flag\nis used to look for the next data chunk with SV bit set, after\nfailures like buffer overflow, buffer allocation failure, skb pointer\nvalidity besides buffer overflow error.\n\nNot writing to status0 if it reads 0.",
  "epss": {
    "percentage": 0.00185,
    "percentile": 0.07267
  },
  "ghsa_id": "GHSA-f226-mgwm-5x89",
  "github_reviewed_at": null,
  "html_url": "https://github.com/advisories/GHSA-f226-mgwm-5x89",
  "identifiers": [
    {
      "type": "GHSA",
      "value": "GHSA-f226-mgwm-5x89"
    },
    {
      "type": "CVE",
      "value": "CVE-2026-98105"
    }
  ],
  "nvd_published_at": "2026-09-25T11:17:40Z",
  "published_at": "2026-09-25T12:31:36Z",
  "references": [
    "https://nvd.nist.gov/vuln/detail/CVE-2026-98105",
    "https://git.kernel.org/stable/c/172c974113bffe5723b80b1acac17593bb50513c",
    "https://git.kernel.org/stable/c/9d3f6e714d5f8b728837f31bbe865b64cfd3216a",
    "https://git.kernel.org/stable/c/b89770d493749d7c3b8649996e1089719b4eff8d",
    "https://git.kernel.org/stable/c/d33003e752f25c385f2cf21964123582a44f6818",
    "https://github.com/advisories/GHSA-f226-mgwm-5x89"
  ],
  "repository_advisory_url": null,
  "severity": "unknown",
  "source_code_location": "",
  "summary": "In the Linux kernel, the following vulnerability has been resolved:\n\nnet: ethernet: oa_tc6:...",
  "type": "unreviewed",
  "updated_at": "2026-09-25T12:31:48Z",
  "url": "https://api.github.com/advisories/GHSA-f226-mgwm-5x89",
  "vulnerabilities": [],
  "withdrawn_at": null
}

Text

In the Linux kernel, the following vulnerability has been resolved: net: ethernet: oa_tc6:... In the Linux kernel, the following vulnerability has been resolved: net: ethernet: oa_tc6: Improve the error recovery When oversubscribed traffic causes lot of buffer overflow errors, probably due to loss of data chunks, driver fails to find a data chunk with end_valid bit set, before it runs out of sk buffer space. As a result, assert is seen during skb_put. Now, check is made if skb buffer has enough tailroom for the incoming data before accepting. If there is no room, current frame is abandoned and it will start looking for a data chunk with start_valid bit, that is a new frame. SK buffer allocation error is considered as recoverable error. rx_buf_overflow flag is too specific and no longer the only condition this flag is used for. Therefore it is renamed as wait_until_start_valid. This is more appropriate as this flag is used to look for the next data chunk with SV bit set, after failures like buffer overflow, buffer allocation failure, skb pointer validity besides buffer overflow error. Not writing to status0 if it reads 0.