ghsa-hm28-rwr4-j8f5
Vulnerability from github
Published
2024-09-27 15:30
Modified
2024-11-20 15:30
Severity ?
Details
In the Linux kernel, the following vulnerability has been resolved:
kunit/overflow: Fix UB in overflow_allocation_test
The 'device_name' array doesn't exist out of the 'overflow_allocation_test' function scope. However, it is being used as a driver name when calling 'kunit_driver_create' from 'kunit_device_register'. It produces the kernel panic with KASAN enabled.
Since this variable is used in one place only, remove it and pass the device name into kunit_device_register directly as an ascii string.
{ "affected": [], "aliases": [ "CVE-2024-46823" ], "database_specific": { "cwe_ids": [], "github_reviewed": false, "github_reviewed_at": null, "nvd_published_at": "2024-09-27T13:15:14Z", "severity": "MODERATE" }, "details": "In the Linux kernel, the following vulnerability has been resolved:\n\nkunit/overflow: Fix UB in overflow_allocation_test\n\nThe \u0027device_name\u0027 array doesn\u0027t exist out of the\n\u0027overflow_allocation_test\u0027 function scope. However, it is being used as\na driver name when calling \u0027kunit_driver_create\u0027 from\n\u0027kunit_device_register\u0027. It produces the kernel panic with KASAN\nenabled.\n\nSince this variable is used in one place only, remove it and pass the\ndevice name into kunit_device_register directly as an ascii string.", "id": "GHSA-hm28-rwr4-j8f5", "modified": "2024-11-20T15:30:49Z", "published": "2024-09-27T15:30:33Z", "references": [ { "type": "ADVISORY", "url": "https://nvd.nist.gov/vuln/detail/CVE-2024-46823" }, { "type": "WEB", "url": "https://git.kernel.org/stable/c/92e9bac18124682c4b99ede9ee3bcdd68f121e92" }, { "type": "WEB", "url": "https://git.kernel.org/stable/c/d1207f07decc66546a7fa463d2f335a856c986ef" } ], "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" } ] }
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.