drm/amd/display: use proper context for logging
No exploitation in the wild has been reported. EPSS puts the chance of exploitation in the next 30 days at 0%. Fixed in Kernel f556bc844cc4423e5ad41ae41a4c24f1cf75b978, Kernel 02647d98340738f918690ed227fdcf154db1b84a, Kernel 07b52a41765722ec971e0cd9739b140bf4933998 and 6 more.
In the Linux kernel, the following vulnerability has been resolved: drm/amd/display: use proper context for logging The same as the rest of the code, get_ss_info_from_atombios() uses calc_pll_cs->ctx->logger for logging. But calc_pll_cs->ctx is initialized only later in calc_pll_max_vco_construct(). Therefore, any output using DC_LOG_SYNC() leads to a NULL pointer deference in get_ss_info_from_atombios(). According to Sashiko, the very same problem exists in dce112_get_pix_clk_dividers() and dcn3_get_pix_clk_dividers() too. To avoid accessing the NULL context, use clk_src->base.ctx->logger everywhere. That context in base is initialized earlier in dce110_clk_src_construct() and dce112_clk_src_construct(). Before get_ss_info_from_atombios() or Sashiko's get_pix_clk_dividers functions above are actually called. This is done by redefining DC_LOGGER to CTX->logger. Before: dce110_clk_src_construct() did: -> sets clk_src->base.ctx = ctx; -> ss_info_from_atombios_create() -> get_ss_info_from_atombios() <- uses calc_pll_cs->ctx # BOOM -> calc_pll_max_vco_construct() <- sets calc_pll_cs->ctx After: dce110_clk_src_construct() does: -> sets clk_src->base.ctx = ctx; -> ss_info_from_atombios_create() -> get_ss_info_from_atombios() <- uses clk_src->base.ctx (cherry picked from commit 6f16fcbb0c46a87e3d9685407e906573d60104b0)
Affected
Vendors, products and packages with version ranges
| Vendor | Product | Versions | Fixed |
|---|---|---|---|
| Linux | Kernel | >=1296423bf23c7a58133970e223b1f47ec6570308 <f556bc844cc4423e5ad41ae41a4c24f1cf75b978, >=1296423bf23c7a58133970e223b1f47ec6570308 <02647d98340738f918690ed227fdcf154db1b84a, >=1296423bf23c7a58133970e223b1f47ec6570308 <07b52a41765722ec971e0cd9739b140bf4933998, >=1296423bf23c7a58133970e223b1f47ec6570308 <114b42507b6a23d9d24e24e4ef165233332c64d4, >=1296423bf23c7a58133970e223b1f47ec6570308 <a94e62b7c7018fcfe0251e53fa96af30f12d923a, =4.17 | f556bc844cc4423e5ad41ae41a4c24f1cf75b978, 02647d98340738f918690ed227fdcf154db1b84a, 07b52a41765722ec971e0cd9739b140bf4933998, 114b42507b6a23d9d24e24e4ef165233332c64d4, a94e62b7c7018fcfe0251e53fa96af30f12d923a |
| linux-kernel: Kernel | >=6.13.0 <6.18.44, >=6.19.0 <7.1.8, >=6.7.0 <6.12.103, >=4.17.0 <6.6.160 | 6.18.44, 7.1.8, 6.12.103, 6.6.160 |
Timeline
Every event on this vulnerability
Related
Other vulnerabilities in Kernel, strongest first
Embed
A live severity badge for an advisory, README or ticket