9.3

CVE-2022-26757

A use after free issue was addressed with improved memory management. This issue is fixed in tvOS 15.5, iOS 15.5 and iPadOS 15.5, Security Update 2022-004 Catalina, watchOS 8.6, macOS Big Sur 11.6.6, macOS Monterey 12.4. An application may be able to execute arbitrary code with kernel privileges.

Data is provided by the National Vulnerability Database (NVD)
Apple ≫ iPadOS Version < 15.5
Apple ≫ iPhone OS Version < 15.5
Apple ≫ macOS X Version < 10.15.7
Apple ≫ macOS X Version10.15.7 Update-
Apple ≫ macOS X Version10.15.7 Updatesecurity_update_2020-001
Apple ≫ macOS X Version10.15.7 Updatesecurity_update_2021-001
Apple ≫ macOS X Version10.15.7 Updatesecurity_update_2021-002
Apple ≫ macOS X Version10.15.7 Updatesecurity_update_2021-003
Apple ≫ macOS X Version10.15.7 Updatesecurity_update_2021-004
Apple ≫ macOS X Version10.15.7 Updatesecurity_update_2021-005
Apple ≫ macOS X Version10.15.7 Updatesecurity_update_2021-006
Apple ≫ macOS X Version10.15.7 Updatesecurity_update_2021-007
Apple ≫ macOS X Version10.15.7 Updatesecurity_update_2021-008
Apple ≫ macOS X Version10.15.7 Updatesecurity_update_2022-001
Apple ≫ macOS X Version10.15.7 Updatesecurity_update_2022-002
Apple ≫ macOS X Version10.15.7 Updatesecurity_update_2022-003
Apple ≫ macOS Version >= 11.0 < 11.6.6
Apple ≫ macOS Version >= 12.0 < 12.4
Apple ≫ tvOS Version < 15.5
Apple ≫ watchOS Version < 8.6
Zu dieser CVE wurde keine CISA KEV oder CERT.AT-Warnung gefunden.
EPSS Metriken
Type Source Score Percentile
EPSS FIRST.org 4.04% 0.88
CVSS Metriken
Source Base Score Exploit Score Impact Score Vector string
nvd@nist.gov 7.8 1.8 5.9
CVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H
nvd@nist.gov 9.3 8.6 10
AV:N/AC:M/Au:N/C:C/I:C/A:C
CWE-416 Use After Free

The product reuses or references memory after it has been freed. At some point afterward, the memory may be allocated again and saved in another pointer, while the original pointer references a location somewhere within the new allocation. Any operations using the original pointer are no longer valid because the memory "belongs" to the code that operates on the new pointer.