ghsa-mrjm-phcf-g3vg
Vulnerability from github
Published
2024-10-21 12:30
Modified
2024-11-08 18:30
Severity ?
Details
In the Linux kernel, the following vulnerability has been resolved:
drivers: media: dvb-frontends/rtl2830: fix an out-of-bounds write error
Ensure index in rtl2830_pid_filter does not exceed 31 to prevent out-of-bounds access.
dev->filters is a 32-bit value, so set_bit and clear_bit functions should only operate on indices from 0 to 31. If index is 32, it will attempt to access a non-existent 33rd bit, leading to out-of-bounds access. Change the boundary check from index > 32 to index >= 32 to resolve this issue.
{ affected: [], aliases: [ "CVE-2024-47697", ], database_specific: { cwe_ids: [ "CWE-787", ], github_reviewed: false, github_reviewed_at: null, nvd_published_at: "2024-10-21T12:15:06Z", severity: "HIGH", }, details: "In the Linux kernel, the following vulnerability has been resolved:\n\ndrivers: media: dvb-frontends/rtl2830: fix an out-of-bounds write error\n\nEnsure index in rtl2830_pid_filter does not exceed 31 to prevent\nout-of-bounds access.\n\ndev->filters is a 32-bit value, so set_bit and clear_bit functions should\nonly operate on indices from 0 to 31. If index is 32, it will attempt to\naccess a non-existent 33rd bit, leading to out-of-bounds access.\nChange the boundary check from index > 32 to index >= 32 to resolve this\nissue.", id: "GHSA-mrjm-phcf-g3vg", modified: "2024-11-08T18:30:44Z", published: "2024-10-21T12:30:55Z", references: [ { type: "ADVISORY", url: "https://nvd.nist.gov/vuln/detail/CVE-2024-47697", }, { type: "WEB", url: "https://git.kernel.org/stable/c/042b101d7bf70616c4967c286ffa6fcca65babfb", }, { type: "WEB", url: "https://git.kernel.org/stable/c/3dba83d3c81de1368d15a39f22df7b53e306052f", }, { type: "WEB", url: "https://git.kernel.org/stable/c/46d7ebfe6a75a454a5fa28604f0ef1491f9d8d14", }, { type: "WEB", url: "https://git.kernel.org/stable/c/58f31be7dfbc0c84a6497ad51924949cf64b86a2", }, { type: "WEB", url: "https://git.kernel.org/stable/c/7fd6aae7e53b94f4035b1bfce28b8dfa0d0ae470", }, { type: "WEB", url: "https://git.kernel.org/stable/c/86d920d2600c3a48efc2775c1666c1017eec6956", }, { type: "WEB", url: "https://git.kernel.org/stable/c/883f794c6e498ae24680aead55c16f66b06cfc30", }, { type: "WEB", url: "https://git.kernel.org/stable/c/8ffbe7d07b8e76193b151107878ddc1ccc94deb5", }, { type: "WEB", url: "https://git.kernel.org/stable/c/badbd736e6649c4e6d7b4ff7e2b9857acfa9ea94", }, ], schema_version: "1.4.0", severity: [ { score: "CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H", type: "CVSS_V3", }, ], }
Log in or create an account to share your comment.
Security Advisory comment format.
This schema specifies the format of a comment related to a security advisory.
Title of the comment
Description of the comment
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.