GHSA-9VR4-4R2H-JQV2

Vulnerability from github – Published: 2026-09-25 12:31 – Updated: 2026-10-26 21:35
VLAI
Details

In the Linux kernel, the following vulnerability has been resolved:

netfs: break unbuffered write when netfs_alloc_subrequest() fails

syzbot reported a null-ptr-deref below [1] following a fault injection in netfs_alloc_subrequest(). [0]

When netfs_alloc_subrequest() fails, subreq is NULL. Later, netfs_prepare_write() tries to initialize members of subreq(e.g., source), the issue in [1] is triggered.

Let's handle the error of netfs_prepare_write() properly.

[0] FAULT_INJECTION: forcing a failure. name failslab, interval 1, probability 0, space 0, times 0 Call Trace: netfs_alloc_subrequest+0x116/0x3f0 netfs_prepare_write+0x76/0x7b0 netfs_unbuffered_write+0x75c/0x2020 netfs_unbuffered_write_iter_locked+0x7d6/0xa80 netfs_unbuffered_write_iter+0x442/0x720 v9fs_file_write_iter+0xbf/0x100 vfs_write+0x6ac/0x1050

[1] KASAN: null-ptr-deref in range [0x00000000000000a8-0x00000000000000af] RIP: 0010:netfs_prepare_write+0xbc/0x7b0 fs/netfs/write_issue.c:173 Call Trace: netfs_unbuffered_write+0x75c/0x2020 fs/netfs/direct_write.c:111 netfs_unbuffered_write_iter_locked+0x7d6/0xa80 fs/netfs/direct_write.c:290 netfs_unbuffered_write_iter+0x442/0x720 fs/netfs/direct_write.c:382 v9fs_file_write_iter+0xbf/0x100 fs/9p/vfs_file.c:409 new_sync_write fs/read_write.c:595 [inline]

Show details on source website

{
  "affected": [],
  "aliases": [
    "CVE-2026-98119"
  ],
  "database_specific": {
    "cwe_ids": [
      "CWE-476"
    ],
    "github_reviewed": false,
    "github_reviewed_at": null,
    "nvd_published_at": "2026-09-25T11:17:43Z",
    "severity": "MODERATE"
  },
  "details": "In the Linux kernel, the following vulnerability has been resolved:\n\nnetfs: break unbuffered write when netfs_alloc_subrequest() fails\n\nsyzbot reported a null-ptr-deref below [1] following a fault injection in\nnetfs_alloc_subrequest(). [0]\n\nWhen netfs_alloc_subrequest() fails, subreq is NULL.\nLater, netfs_prepare_write() tries to initialize members of\nsubreq(e.g., source), the issue in [1] is triggered.\n\nLet\u0027s handle the error of netfs_prepare_write() properly.\n\n[0]\nFAULT_INJECTION: forcing a failure.\nname failslab, interval 1, probability 0, space 0, times 0\nCall Trace:\n netfs_alloc_subrequest+0x116/0x3f0\n netfs_prepare_write+0x76/0x7b0\n netfs_unbuffered_write+0x75c/0x2020\n netfs_unbuffered_write_iter_locked+0x7d6/0xa80\n netfs_unbuffered_write_iter+0x442/0x720\n v9fs_file_write_iter+0xbf/0x100\n vfs_write+0x6ac/0x1050\n\n[1]\nKASAN: null-ptr-deref in range [0x00000000000000a8-0x00000000000000af]\nRIP: 0010:netfs_prepare_write+0xbc/0x7b0 fs/netfs/write_issue.c:173\nCall Trace:\n netfs_unbuffered_write+0x75c/0x2020 fs/netfs/direct_write.c:111\n netfs_unbuffered_write_iter_locked+0x7d6/0xa80 fs/netfs/direct_write.c:290\n netfs_unbuffered_write_iter+0x442/0x720 fs/netfs/direct_write.c:382\n v9fs_file_write_iter+0xbf/0x100 fs/9p/vfs_file.c:409\n new_sync_write fs/read_write.c:595 [inline]",
  "id": "GHSA-9vr4-4r2h-jqv2",
  "modified": "2026-10-26T21:35:45Z",
  "published": "2026-09-25T12:31:37Z",
  "references": [
    {
      "type": "ADVISORY",
      "url": "https://nvd.nist.gov/vuln/detail/CVE-2026-98119"
    },
    {
      "type": "WEB",
      "url": "https://git.kernel.org/stable/c/19f246c795e940dc5f11cd5bc0cb1e81bc7b7090"
    },
    {
      "type": "WEB",
      "url": "https://git.kernel.org/stable/c/8fb45a934661419c04a44d4cfea1e0df7dcf2805"
    },
    {
      "type": "WEB",
      "url": "https://git.kernel.org/stable/c/cf6f93b8b06acf57de62dacbe71a3b99c68656a7"
    }
  ],
  "schema_version": "1.4.0",
  "severity": [
    {
      "score": "CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H",
      "type": "CVSS_V3"
    }
  ]
}



Log in or create an account to share your comment.




Tags
Taxonomy of the tags.


Loading…

Loading…

Loading…

Drag nodes to arrange them. Double-click a related vulnerability to open it, or a source to visit its link. The Physics button on the left tunes the layout and the simulation; the legend at the bottom left hides or shows nodes by kind and by sighting type.

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.
Vulnerability timeline

Sightings and recorded dates, grouped by day · UTC

JSON
How durations are calculated

Following the VTEM framework (Black Hat USA 2015), time to patch starts when the vendor or a coordinator was informed, total time to patch at discovery, and disclosure to patch at public disclosure; vendor response time runs from the report to its acknowledgement. Time to exploit and time unpatched start at the earliest discovery or report, falling back to public disclosure. Unpatched time ends at the first recorded patch, or the calculation time when no patch is recorded. Exploitation to patch shows the interval between those two events; a published proof of concept is a public exploit, not exploitation.

Each result shows its source dates. A negative interval means the end event came first; when date-only inputs leave the order open, the result says so. Date-only inputs are approximate. The earliest evidence wins: KEV report dates and sightings are labelled as such. Records describing another vulnerability are listed but never calculated from, and a PoC alone does not establish exploitation. Missing patch evidence does not prove that no patch exists. Filters below change the event list only.

Events included in the timeline

Loading timeline…


    Loading…

    Loading…

    Loading…

    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.