CVE-2023-53087— Linux kernel 安全漏洞
一分钟漏洞结论
影响对象
Linux Linux
利用判断
尚无明确在野利用证据，仍需结合暴露面评估
建议动作
优先检查厂商安全公告和参考链接中的修复版本；无法立即升级时，限制受影响服务暴露并加强监测。
Linux kernel是美国Linux基金会的开源操作系统Linux所使用的内核。 Linux kernel存在安全漏洞，该漏洞源于drm_i915_active错误使用非空闲屏障。
可能的 ATT&CK 技术 1 AI
T1068 · Exploitation for Privilege Escalation影响版本矩阵 12
| 厂商 | 产品 | 版本范围 | 状态 |
|---|---|---|---|
| Linux | Linux | 311770173fac27845a3a83e2c16100a54d308f72< 5e784a7d07af42057c0576fb647b482f4cb0dc2c |
affected |
311770173fac27845a3a83e2c16100a54d308f72< 6ab7d33617559cced63d467928f478ea5c459021 |
affected | ||
311770173fac27845a3a83e2c16100a54d308f72< 5c7591b8574c52c56b3994c2fbef1a3a311b5715 |
affected | ||
311770173fac27845a3a83e2c16100a54d308f72< 9159db27fb19bbf1c91b5c9d5285e66cc96cc5ff |
affected | ||
311770173fac27845a3a83e2c16100a54d308f72< e0e6b416b25ee14716f3549e0cbec1011b193809 |
affected | ||
5.5 |
affected | ||
< 5.5 |
unaffected | ||
5.10.176≤ 5.10.* |
unaffected | ||
| … +4 条更多 | |||
获取后续新漏洞提醒
登录后订阅
一、 漏洞 CVE-2023-53087 基础信息
漏洞信息
对漏洞内容有疑问？看看神龙的深度分析是否有帮助！
查看神龙十问 ↗
尽管我们使用了先进的大模型技术，但其输出仍可能包含不准确或过时的信息。神龙努力确保数据的准确性，但请您根据实际情况进行核实和判断。
Vulnerability Title
drm/i915/active: Fix misuse of non-idle barriers as fence trackers
来源: CVE Program / CVE List V5
Vulnerability Description
In the Linux kernel, the following vulnerability has been resolved:
drm/i915/active: Fix misuse of non-idle barriers as fence trackers
Users reported oopses on list corruptions when using i915 perf with a
number of concurrently running graphics applications. Root cause analysis
pointed at an issue in barrier processing code -- a race among perf open /
close replacing active barriers with perf requests on kernel context and
concurrent barrier preallocate / acquire operations performed during user
context first pin / last unpin.
When adding a request to a composite tracker, we try to reuse an existing
fence tracker, already allocated and registered with that composite. The
tracker we obtain may already track another fence, may be an idle barrier,
or an active barrier.
If the tracker we get occurs a non-idle barrier then we try to delete that
barrier from a list of barrier tasks it belongs to. However, while doing
that we don't respect return value from a function that performs the
barrier deletion. Should the deletion ever fail, we would end up reusing
the tracker still registered as a barrier task. Since the same structure
field is reused with both fence callback lists and barrier tasks list,
list corruptions would likely occur.
Barriers are now deleted from a barrier tasks list by temporarily removing
the list content, traversing that content with skip over the node to be
deleted, then populating the list back with the modified content. Should
that intentionally racy concurrent deletion attempts be not serialized,
one or more of those may fail because of the list being temporary empty.
Related code that ignores the results of barrier deletion was initially
introduced in v5.4 by commit d8af05ff38ae ("drm/i915: Allow sharing the
idle-barrier from other kernel requests"). However, all users of the
barrier deletion routine were apparently serialized at that time, then the
issue didn't exhibit itself. Results of git bisect with help of a newly
developed igt@gem_barrier_race@remote-request IGT test indicate that list
corruptions might start to appear after commit 311770173fac ("drm/i915/gt:
Schedule request retirement when timeline idles"), introduced in v5.5.
Respect results of barrier deletion attempts -- mark the barrier as idle
only if successfully deleted from the list. Then, before proceeding with
setting our fence as the one currently tracked, make sure that the tracker
we've got is not a non-idle barrier. If that check fails then don't use
that tracker but go back and try to acquire a new, usable one.
v3: use unlikely() to document what outcome we expect (Andi),
- fix bad grammar in commit description.
v2: no code changes,
- blame commit 311770173fac ("drm/i915/gt: Schedule request retirement
when timeline idles"), v5.5, not commit d8af05ff38ae ("drm/i915: Allow
sharing the idle-barrier from other kernel requests"), v5.4,
- reword commit description.
(cherry picked from commit 506006055769b10d1b2b4e22f636f3b45e0e9fc7)
来源: CVE Program / CVE List V5
CVSS Information
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
来源: CVE Program / CVE List V5
Vulnerability Type
N/A
来源: CVE Program / CVE List V5
Vulnerability Title
Linux kernel 安全漏洞
来源: 中国国家信息安全漏洞库 CNNVD
Vulnerability Description
Linux kernel是美国Linux基金会的开源操作系统Linux所使用的内核。 Linux kernel存在安全漏洞，该漏洞源于drm_i915_active错误使用非空闲屏障。
来源: 中国国家信息安全漏洞库 CNNVD
CVSS Information
N/A
来源: 中国国家信息安全漏洞库 CNNVD
Vulnerability Type
N/A
来源: 中国国家信息安全漏洞库 CNNVD
受影响产品
二、漏洞 CVE-2023-53087 的公开POC
| # | POC 描述 | 源链接 | 神龙链接 |
|---|
AI 生成 POC
高级
未找到公开 POC。
登录以生成 AI POC三、漏洞 CVE-2023-53087 的情报信息
请登录查看更多情报信息。
CVE-2023-53087 补丁与修复 (5)
同批安全公告 · Linux · 2025-05-02 · 共 107 条
| CVE-2023-53116 | 9.8 CRITICAL | Linux kernel 安全漏洞 |
| CVE-2023-53083 | 9.8 CRITICAL | Linux kernel 安全漏洞 |
| CVE-2023-53086 | 8.8 HIGH | Linux kernel 安全漏洞 |
| CVE-2025-37798 | 7.8 HIGH | Linux kernel 安全漏洞 |
| CVE-2023-53138 | 7.8 HIGH | Linux kernel 安全漏洞 |
| CVE-2023-53111 | 7.8 HIGH | Linux kernel 安全漏洞 |
| CVE-2023-53107 | 7.8 HIGH | Linux kernel 安全漏洞 |
| CVE-2023-53102 | 7.8 HIGH | Linux kernel 安全漏洞 |
| CVE-2023-53100 | 7.8 HIGH | Linux kernel 安全漏洞 |
| CVE-2023-53094 | 7.8 HIGH | Linux kernel 安全漏洞 |
| CVE-2023-53090 | 7.8 HIGH | Linux kernel 安全漏洞 |
| CVE-2023-53088 | 7.8 HIGH | Linux kernel 安全漏洞 |
| CVE-2023-53084 | 7.8 HIGH | Linux kernel 安全漏洞 |
| CVE-2023-53080 | 7.8 HIGH | Linux kernel 安全漏洞 |
| CVE-2023-53072 | 7.8 HIGH | Linux kernel 安全漏洞 |
| CVE-2023-53065 | 7.8 HIGH | Linux kernel 安全漏洞 |
| CVE-2023-53057 | 7.8 HIGH | Linux kernel 安全漏洞 |
| CVE-2023-53052 | 7.8 HIGH | Linux kernel 安全漏洞 |
| CVE-2023-53047 | 7.8 HIGH | Linux kernel 安全漏洞 |
| CVE-2023-53039 | 7.8 HIGH | Linux kernel 安全漏洞 |
显示前 20 条，共 107 条。 查看全部 → →
IV. Related Vulnerabilities
V. Comments for CVE-2023-53087
暂无评论