发布时间: 2025年3月14日
修改时间: 2025年4月25日
In the Linux kernel, the following vulnerability has been resolved: Bluetooth: L2CAP: handle NULL sock pointer in l2cap_sock_alloc A NULL sock pointer is passed into l2cap_sock_alloc() when it is called from l2cap_sock_new_connection_cb() and the error handling paths should also be aware of it. Seemingly a more elegant solution would be to swap bt_sock_alloc() and l2cap_chan_create() calls since they are not interdependent to that moment but then l2cap_chan_create() adds the soon to be deallocated and still dummy-initialized channel to the global list accessible by many L2CAP paths. The channel would be removed from the list in short period of time but be a bit more straight-forward here and just check for NULL instead of changing the order of function calls. Found by Linux Verification Center (linuxtesting.org) with SVACE static analysis tool.
NVD | openEuler | |
---|---|---|
Confidentiality | Low | |
Attack Vector | Local | |
CVSS评分 | N/A | 3.9 |
Attack Complexity | High | |
Privileges Required | High | |
Scope | Unchanged | |
Integrity | Low | |
User Interaction | None | |
Availability | Low |
公告名 | 概要 | 发布时间 |
---|---|---|
KylinSec-SA-2025-2717 | kernel security update | 2025年6月11日 |
产品 | 包 | 状态 |
---|---|---|
KY3.4-5A | kernel | Fixed |
V6 | kernel | Fixed |
KY3.5.3 | kernel | Fixed |
KY3.5.2 | kernel | Fixed |