fkie_cve-2024-46748
Vulnerability from fkie_nvd
Published
2024-09-18 08:15
Modified
2024-09-20 12:30
Severity ?
Summary
In the Linux kernel, the following vulnerability has been resolved: cachefiles: Set the max subreq size for cache writes to MAX_RW_COUNT Set the maximum size of a subrequest that writes to cachefiles to be MAX_RW_COUNT so that we don't overrun the maximum write we can make to the backing filesystem.
Impacted products
Vendor Product Version



{
  "cveTags": [],
  "descriptions": [
    {
      "lang": "en",
      "value": "In the Linux kernel, the following vulnerability has been resolved:\n\ncachefiles: Set the max subreq size for cache writes to MAX_RW_COUNT\n\nSet the maximum size of a subrequest that writes to cachefiles to be\nMAX_RW_COUNT so that we don\u0027t overrun the maximum write we can make to the\nbacking filesystem."
    },
    {
      "lang": "es",
      "value": "En el kernel de Linux, se ha resuelto la siguiente vulnerabilidad: cachefiles: Establezca el tama\u00f1o m\u00e1ximo de subsolicitud para escrituras de cach\u00e9 en MAX_RW_COUNT Establezca el tama\u00f1o m\u00e1ximo de una subsolicitud que escribe en cachefiles en MAX_RW_COUNT para que no sobrepasemos la escritura m\u00e1xima que podemos realizar en el sistema de archivos de respaldo."
    }
  ],
  "id": "CVE-2024-46748",
  "lastModified": "2024-09-20T12:30:51.220",
  "metrics": {},
  "published": "2024-09-18T08:15:03.847",
  "references": [
    {
      "source": "416baaa9-dc9f-4396-8d5f-8c081fb06d67",
      "url": "https://git.kernel.org/stable/c/51d37982bbac3ea0ca21b2797a9cb0044272b3aa"
    },
    {
      "source": "416baaa9-dc9f-4396-8d5f-8c081fb06d67",
      "url": "https://git.kernel.org/stable/c/cec226f9b1fd6cf55bc157873aec61b523083e96"
    }
  ],
  "sourceIdentifier": "416baaa9-dc9f-4396-8d5f-8c081fb06d67",
  "vulnStatus": "Awaiting Analysis"
}


Log in or create an account to share your comment.




Tags
Taxonomy of the tags.


Loading…

Loading…

Loading…

Sightings

Author Source Type Date

Nomenclature

  • Seen: The vulnerability was mentioned, discussed, or seen somewhere by the user.
  • Confirmed: The vulnerability is confirmed from an analyst perspective.
  • Exploited: This vulnerability was exploited and seen by the user reporting the sighting.
  • Patched: This vulnerability was successfully patched by the user reporting the sighting.
  • Not exploited: This vulnerability was not exploited or seen by the user reporting the sighting.
  • Not confirmed: The user expresses doubt about the veracity of the vulnerability.
  • Not patched: This vulnerability was not successfully patched by the user reporting the sighting.


Loading…

Loading…