ghsa-xqr4-wc4c-36xj
Vulnerability from github
Published
2024-09-04 21:30
Modified
2024-09-05 18:30
Severity ?
Details
In the Linux kernel, the following vulnerability has been resolved:
net: dsa: bcm_sf2: Fix a possible memory leak in bcm_sf2_mdio_register()
bcm_sf2_mdio_register() calls of_phy_find_device() and then phy_device_remove() in a loop to remove existing PHY devices. of_phy_find_device() eventually calls bus_find_device(), which calls get_device() on the returned struct device * to increment the refcount. The current implementation does not decrement the refcount, which causes memory leak.
This commit adds the missing phy_device_free() call to decrement the refcount via put_device() to balance the refcount.
{ affected: [], aliases: [ "CVE-2024-44971", ], database_specific: { cwe_ids: [ "CWE-401", ], github_reviewed: false, github_reviewed_at: null, nvd_published_at: "2024-09-04T19:15:31Z", severity: "MODERATE", }, details: "In the Linux kernel, the following vulnerability has been resolved:\n\nnet: dsa: bcm_sf2: Fix a possible memory leak in bcm_sf2_mdio_register()\n\nbcm_sf2_mdio_register() calls of_phy_find_device() and then\nphy_device_remove() in a loop to remove existing PHY devices.\nof_phy_find_device() eventually calls bus_find_device(), which calls\nget_device() on the returned struct device * to increment the refcount.\nThe current implementation does not decrement the refcount, which causes\nmemory leak.\n\nThis commit adds the missing phy_device_free() call to decrement the\nrefcount via put_device() to balance the refcount.", id: "GHSA-xqr4-wc4c-36xj", modified: "2024-09-05T18:30:56Z", published: "2024-09-04T21:30:32Z", references: [ { type: "ADVISORY", url: "https://nvd.nist.gov/vuln/detail/CVE-2024-44971", }, { type: "WEB", url: "https://git.kernel.org/stable/c/7feef10768ea71d468d9bbc1e0d14c461876768c", }, { type: "WEB", url: "https://git.kernel.org/stable/c/a7d2808d67570e6acae45c2a96e0d59986888e4c", }, { type: "WEB", url: "https://git.kernel.org/stable/c/b7b8d9f5e679af60c94251fd6728dde34be69a71", }, { type: "WEB", url: "https://git.kernel.org/stable/c/c05516c072903f6fb9134b8e7e1ad4bffcdc4819", }, { type: "WEB", url: "https://git.kernel.org/stable/c/e3862093ee93fcfbdadcb7957f5f8974fffa806a", }, { type: "WEB", url: "https://git.kernel.org/stable/c/f3d5efe18a11f94150fee8b3fda9d62079af640a", }, ], 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.
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.