Answer in brief
CVE-2022-49530 records a Unknown severity vulnerability in drm/amd/pm: fix double free in si_parse_power_table(). The current sources do not mark it as known exploited. The current feed maps Linux/Linux (generic), Linux/Linux (generic). Check affected ranges and fixed versions before updating.
Analysis pending evidence review
HOL Guard separates source facts from reviewed analysis. See the methodology.
Answer in brief
CVE-2022-49530 records a Unknown severity vulnerability in drm/amd/pm: fix double free in si_parse_power_table(). The current sources do not mark it as known exploited. The current feed maps Linux/Linux (generic), Linux/Linux (generic). Check affected ranges and fixed versions before updating.
Analysis pending evidence review
HOL Guard separates source facts from reviewed analysis. See the methodology.
A CVSS score is not reported in the current record. The current sources do not mark it as known exploited. Treat this as a source-backed prioritization signal, not a statement about your environment.
Analysis status
Analysis pending evidence review
Factual feed record only; HOL analysis is not approved for indexing. Read the methodology.
The current feed maps Linux/Linux (generic), Linux/Linux (generic). Check affected ranges and fixed versions before updating.
| Package | Affected range | Fixed version |
|---|---|---|
| Linux/Linuxgeneric | >=841686df9f7d2942cfd94d024b8591fa3f74ef7c <2615464854505188f909d0c07c37a6623693b5c7 || >=841686df9f7d2942cfd94d024b8591fa3f74ef7c <6c5bdaa1325be7f04b79ea992ab216739192d342 || >=841686df9f7d2942cfd94d024b8591fa3f74ef7c <c0e811c4ccf3b42705976285e3a94cc82dea7300 || >=841686df9f7d2942cfd94d024b8591fa3f74ef7c <af832028af6f44c6c45645757079c4ed6884ade5 || >=841686df9f7d2942cfd94d024b8591fa3f74ef7c <ca1ce206894dd976275c78ee38dbc19873f22de9 || >=841686df9f7d2942cfd94d024b8591fa3f74ef7c <a5ce7051db044290b1a95045ff03c249005a3aa4 || >=841686df9f7d2942cfd94d024b8591fa3f74ef7c <fd2eff8b9dcbe469c3b7bbbc7083ab5ed94de07b || >=841686df9f7d2942cfd94d024b8591fa3f74ef7c <43eb9b667b95f2a31c63e8949b0d2161b9be59c3 || >=841686df9f7d2942cfd94d024b8591fa3f74ef7c <f3fa2becf2fc25b6ac7cf8d8b1a2e4a86b3b72bd | 2615464854505188f909d0c07c37a6623693b5c7, 6c5bdaa1325be7f04b79ea992ab216739192d342, c0e811c4ccf3b42705976285e3a94cc82dea7300, af832028af6f44c6c45645757079c4ed6884ade5, ca1ce206894dd976275c78ee38dbc19873f22de9, a5ce7051db044290b1a95045ff03c249005a3aa4, fd2eff8b9dcbe469c3b7bbbc7083ab5ed94de07b, 43eb9b667b95f2a31c63e8949b0d2161b9be59c3, f3fa2becf2fc25b6ac7cf8d8b1a2e4a86b3b72bd |
| Linux/Linuxgeneric | 4.9 | Not reported |
Published upstream
Feb 26, 2025
Evidence: source:cvelist:source_dates:source-dates:recordSource modified
Aug 5, 2026
Evidence: source:cvelist:source_dates:source-dates:recordFirst seen by HOL
Aug 5, 2026
In the Linux kernel, the following vulnerability has been resolved: drm/amd/pm: fix double free in si_parse_power_table() In function si_parse_power_table(), array adev->pm.dpm.ps and its member is allocated. If the allocation of each member fails, the array itself is freed and returned with an error code. However, the array is later freed again in si_dpm_fini() function which is called when the function returns an error. This leads to potential double free of the array adev->pm.dpm.ps, as well as leak of its array members, since the members are not freed in the allocation function and the array is not nulled when freed. In addition adev->pm.dpm.num_ps, which keeps track of the allocated array member, is not updated until the member allocation is successfully finished, this could also lead to either use after free, or uninitialized variable access in si_dpm_fini(). Fix this by postponing the free of the array until si_dpm_fini() and increment adev->pm.dpm.num_ps everytime the array member is allocated.
Quoted source text, attributed separately from HOL analysis.
A CVSS score is not reported in the current record. The current sources do not mark it as known exploited. Treat this as a source-backed prioritization signal, not a statement about your environment.
Analysis status
Analysis pending evidence review
Factual feed record only; HOL analysis is not approved for indexing. Read the methodology.
The current feed maps Linux/Linux (generic), Linux/Linux (generic). Check affected ranges and fixed versions before updating.
| Package | Affected range | Fixed version |
|---|---|---|
| Linux/Linuxgeneric | >=841686df9f7d2942cfd94d024b8591fa3f74ef7c <2615464854505188f909d0c07c37a6623693b5c7 || >=841686df9f7d2942cfd94d024b8591fa3f74ef7c <6c5bdaa1325be7f04b79ea992ab216739192d342 || >=841686df9f7d2942cfd94d024b8591fa3f74ef7c <c0e811c4ccf3b42705976285e3a94cc82dea7300 || >=841686df9f7d2942cfd94d024b8591fa3f74ef7c <af832028af6f44c6c45645757079c4ed6884ade5 || >=841686df9f7d2942cfd94d024b8591fa3f74ef7c <ca1ce206894dd976275c78ee38dbc19873f22de9 || >=841686df9f7d2942cfd94d024b8591fa3f74ef7c <a5ce7051db044290b1a95045ff03c249005a3aa4 || >=841686df9f7d2942cfd94d024b8591fa3f74ef7c <fd2eff8b9dcbe469c3b7bbbc7083ab5ed94de07b || >=841686df9f7d2942cfd94d024b8591fa3f74ef7c <43eb9b667b95f2a31c63e8949b0d2161b9be59c3 || >=841686df9f7d2942cfd94d024b8591fa3f74ef7c <f3fa2becf2fc25b6ac7cf8d8b1a2e4a86b3b72bd | 2615464854505188f909d0c07c37a6623693b5c7, 6c5bdaa1325be7f04b79ea992ab216739192d342, c0e811c4ccf3b42705976285e3a94cc82dea7300, af832028af6f44c6c45645757079c4ed6884ade5, ca1ce206894dd976275c78ee38dbc19873f22de9, a5ce7051db044290b1a95045ff03c249005a3aa4, fd2eff8b9dcbe469c3b7bbbc7083ab5ed94de07b, 43eb9b667b95f2a31c63e8949b0d2161b9be59c3, f3fa2becf2fc25b6ac7cf8d8b1a2e4a86b3b72bd |
| Linux/Linuxgeneric | 4.9 | Not reported |
Published upstream
Feb 26, 2025
Evidence: source:cvelist:source_dates:source-dates:recordSource modified
Aug 5, 2026
Evidence: source:cvelist:source_dates:source-dates:recordFirst seen by HOL
Aug 5, 2026
In the Linux kernel, the following vulnerability has been resolved: drm/amd/pm: fix double free in si_parse_power_table() In function si_parse_power_table(), array adev->pm.dpm.ps and its member is allocated. If the allocation of each member fails, the array itself is freed and returned with an error code. However, the array is later freed again in si_dpm_fini() function which is called when the function returns an error. This leads to potential double free of the array adev->pm.dpm.ps, as well as leak of its array members, since the members are not freed in the allocation function and the array is not nulled when freed. In addition adev->pm.dpm.num_ps, which keeps track of the allocated array member, is not updated until the member allocation is successfully finished, this could also lead to either use after free, or uninitialized variable access in si_dpm_fini(). Fix this by postponing the free of the array until si_dpm_fini() and increment adev->pm.dpm.num_ps everytime the array member is allocated.
Quoted source text, attributed separately from HOL analysis.