CVE-2024-53836

CVE-2024-53836 is a medium-severity vulnerability in Google Android with a CVSS 3.x base score of 6.7. It is not currently listed as actively exploited by CISA, and its EPSS exploit-prediction score is low. The underlying weakness is classified as CWE-787.

Key facts

Description

In wbrc_bt_dev_write of wb_regon_coordinator.c, there is a possible out of bounds write due to a buffer overflow. This could lead to local escalation of privilege with System execution privileges needed. User interaction is not needed for exploitation.

Frequently asked questions

What is CVE-2024-53836?
In wbrc_bt_dev_write of wb_regon_coordinator.c, there is a possible out of bounds write due to a buffer overflow. This could lead to local escalation of privilege with System execution privileges needed. User interaction is not needed for exploitation.
How severe is CVE-2024-53836?
CVE-2024-53836 has a CVSS 3.x base score of 6.7, rated medium severity. It is exploitable over local access with low attack complexity, requires high privileges and no user interaction. Impact on confidentiality is high, integrity high, and availability high.
Is CVE-2024-53836 being actively exploited?
It is not currently listed in CISA's KEV catalog. Its EPSS exploit-prediction score is 0% (1st percentile), an estimate of the probability of exploitation in the next 30 days.
What products are affected by CVE-2024-53836?
CVE-2024-53836 affects Google Android. See the affected-products list for the exact vulnerable versions.
How do I fix CVE-2024-53836?
Review the linked vendor and NVD advisories for patched versions and mitigations, then upgrade or apply the recommended workaround.
Does CVE-2024-53836 have an EU (EUVD) identifier?
Yes. CVE-2024-53836 is tracked in the ENISA EU Vulnerability Database (EUVD) as EUVD-2024-52163.
When was CVE-2024-53836 published?
CVE-2024-53836 was published on 2025-01-03 and last updated on 2026-06-17.

References

Affected products (1)

More vulnerabilities in Google Android

All CVEs affecting Google Android →

Other CWE-787 (Out-of-bounds Write) vulnerabilities

Browse all CWE-787 (Out-of-bounds Write) vulnerabilities →