Bluetooth: RFCOMM: avoid leaving dangling sk pointer in rfcomm_sock_alloc() (Linux Linux)

CVE-2024-56604
HIGH 7.8

At a glance

Source
NVD
EPSS
EPSS 0.22 % · percentile 13 ()
State
PUBLISHED
Published
Updated
Assigner
Linux
NVD status
Modified

Description

In the Linux kernel, the following vulnerability has been resolved: Bluetooth: RFCOMM: avoid leaving dangling sk pointer in rfcomm_sock_alloc() bt_sock_alloc() attaches allocated sk object to the provided sock object. If rfcomm_dlc_alloc() fails, we release the sk object, but leave the dangling pointer in the sock object, which may cause use-after-free. Fix this by swapping calls to bt_sock_alloc() and rfcomm_dlc_alloc().

Weaknesses (CWE)

References

Scores

VersionScoreVectorScored by
CVSS 3.1HIGH 7.8CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:HLinux
CVSS 3.1HIGH 7.8CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:HCISA-ADP
CVSS 3.1HIGH 7.8CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:HNVD · nvd@nist.gov (Primary)
CVSS 3.1HIGH 7.8CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:HNVD · 134c704f-9b21-4f2e-91b3-4a467353bcc0 (Secondary)

European references

CERT-FR advisories

Affected configurations (NVD CPE)

Affected products

ProductVersions
Linux · Linuxaffected 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 < ac3eaac4cf142a15fe67be747a682b1416efeb6e ; affected 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 < 6021ccc2471b7b95e29b7cfc7938e042bf56e281 ; affected 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 < 32df687e129ef0f9afcbcc914f7c32deb28fd481 ; affected 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 < 3945c799f12b8d1f49a3b48369ca494d981ac465
Linux · Linuxaffected 2.6.12 ; unaffected 0 < 2.6.12 ; unaffected 6.1.120 ≤ 6.1.* ; unaffected 6.6.66 ≤ 6.6.* ; unaffected 6.12.5 ≤ 6.12.* ; unaffected 6.13 ≤ *

Sources

SourceLicence
CVE List (CVEProject cvelistV5)CVE Program Terms of Use
EPSS (FIRST.org)FIRST — attribution requested
ENISA EUVDENISA — reproduction authorised, source acknowledged
CERT-FR (ANSSI)Licence Ouverte / Etalab 2.0
NVD (NIST) via fkie-cad/nvd-json-data-feedsPublic domain — this product uses data from the NVD API but is not endorsed or certified by the NVD