GCVE Workshop - 22 September 2026 (14:00-18:00), Luxembourg Before The Vulnopticon Conference - Registration

GHSA-6QRF-JJMP-5PJW

Vulnerability from github – Published: 2026-08-15 15:30 – Updated: 2026-08-15 15:30
VLAI
Details

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

netfs: Fix folio_queue ENOMEM in writeback by adding a mempool

Fix the handling of folio_queue allocation failure in writeback by adding a mempool and passing in gfp_t flags to the rolling buffer functions that allocate memory, using the mempool if gfp != GFP_KERNEL.

This is then extended upwards and the gfp to be used for a request is stored in the netfs_io_request struct and is then used for both requests and subrequests, eliminating the sleeping loops there.

The failure caused:

folio != NULL
WARNING: fs/netfs/write_issue.c:603 at netfs_writepages+0x883/0xa10 fs/netfs/write_issue.c:603, CPU#3: syz.0.17/5919
Show details on source website
To clipboard 

{
  "affected": [],
  "aliases": [
    "CVE-2026-74542"
  ],
  "database_specific": {
    "cwe_ids": [],
    "github_reviewed": false,
    "github_reviewed_at": null,
    "nvd_published_at": "2026-08-15T13:17:59Z",
    "severity": null
  },
  "details": "In the Linux kernel, the following vulnerability has been resolved:\n\nnetfs: Fix folio_queue ENOMEM in writeback by adding a mempool\n\nFix the handling of folio_queue allocation failure in writeback by adding a\nmempool and passing in gfp_t flags to the rolling buffer functions that\nallocate memory, using the mempool if gfp != GFP_KERNEL.\n\nThis is then extended upwards and the gfp to be used for a request is stored\nin the netfs_io_request struct and is then used for both requests and\nsubrequests, eliminating the sleeping loops there.\n\nThe failure caused:\n\n    folio != NULL\n    WARNING: fs/netfs/write_issue.c:603 at netfs_writepages+0x883/0xa10 fs/netfs/write_issue.c:603, CPU#3: syz.0.17/5919",
  "id": "GHSA-6qrf-jjmp-5pjw",
  "modified": "2026-08-15T15:30:36Z",
  "published": "2026-08-15T15:30:36Z",
  "references": [
    {
      "type": "ADVISORY",
      "url": "https://nvd.nist.gov/vuln/detail/CVE-2026-74542"
    },
    {
      "type": "WEB",
      "url": "https://git.kernel.org/stable/c/1d78d56c43ef3768183e8370e7367b162700e049"
    },
    {
      "type": "WEB",
      "url": "https://git.kernel.org/stable/c/3f6d7f8a5416d852648d15a05e895f1195ee8a85"
    }
  ],
  "schema_version": "1.4.0",
  "severity": []
}



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.


Detection rules are retrieved from Rulezet.