摘要:
kernel security update
安全等级: High
公告ID: KylinSec-SA-2024-4991
发布日期: 2025年8月15日
关联CVE: CVE-2024-26944 CVE-2024-36011 CVE-2024-43835 CVE-2024-43911 CVE-2024-44989 CVE-2024-45030 CVE-2024-46678 CVE-2024-46763 CVE-2024-46783 CVE-2024-46835 CVE-2024-47666 CVE-2024-47674 CVE-2024-47723 CVE-2024-47728 CVE-2024-49945 CVE-2024-50056 CVE-2024-50061 CVE-2024-50089 CVE-2024-50099 CVE-2024-50115 CVE-2024-50124 CVE-2024-50138 CVE-2024-50151 CVE-2024-50153 CVE-2024-50180 CVE-2024-50193 CVE-2024-50198 CVE-2024-50202 CVE-2024-50215 CVE-2024-50237 CVE-2024-50242 CVE-2024-50243 CVE-2024-50244 CVE-2024-50245 CVE-2024-50246 CVE-2024-50247 CVE-2024-50250
Linux内核,即操作系统核心本身。
安全修复:
在Linux内核中,以下漏洞已被修复:
btrfs: zoned: 修复do_zone_finish()中的释放后使用问题
Shinichiro报告了在fstests btrfs/070中由设备替换操作触发的以下释放后使用情况。
BTRFS info (device nullb1): scrub: finished on devid 1 with status: 0
==================================================================
BUG: KASAN: slab-use-after-free in do_zone_finish+0x91a/0xb90 [btrfs]
Read of size 8 at addr ffff8881543c8060 by task btrfs-cleaner/3494007
CPU: 0 PID: 3494007 Comm: btrfs-cleaner Tainted: G W 6.8.0-rc5-kts #1
Hardware name: Supermicro Super Server/X11SPi-TF, BIOS 3.3 02/21/2020
Call Trace:
<TASK>
dump_stack_lvl+0x5b/0x90
print_report+0xcf/0x670
? __virt_addr_valid+0x200/0x3e0
kasan_report+0xd8/0x110
? do_zone_finish+0x91a/0xb90 [btrfs]
? do_zone_finish+0x91a/0xb90 [btrfs]
do_zone_finish+0x91a/0xb90 [btrfs]
btrfs_delete_unused_bgs+0x5e1/0x1750 [btrfs]
? __pfx_btrfs_delete_unused_bgs+0x10/0x10 [btrfs]
? btrfs_put_root+0x2d/0x220 [btrfs]
? btrfs_clean_one_deleted_snapshot+0x299/0x430 [btrfs]
cleaner_kthread+0x21e/0x380 [btrfs]
? __pfx_cleaner_kthread+0x10/0x10 [btrfs]
kthread+0x2e3/0x3c0
? __pfx_kthread+0x10/0x10
ret_from_fork+0x31/0x70
? __pfx_kthread+0x10/0x10
ret_from_fork_asm+0x1b/0x30
</TASK>
Allocated by task 3493983:
kasan_save_stack+0x33/0x60
kasan_save_track+0x14/0x30
__kasan_kmalloc+0xaa/0xb0
btrfs_alloc_device+0xb3/0x4e0 [btrfs]
device_list_add.constprop.0+0x993/0x1630 [btrfs]
btrfs_scan_one_device+0x219/0x3d0 [btrfs]
btrfs_control_ioctl+0x26e/0x310 [btrfs]
__x64_sys_ioctl+0x134/0x1b0
do_syscall_64+0x99/0x190
entry_SYSCALL_64_after_hwframe+0x6e/0x76
Freed by task 3494056:
kasan_save_stack+0x33/0x60
kasan_save_track+0x14/0x30
kasan_save_free_info+0x3f/0x60
poison_slab_object+0x102/0x170
__kasan_slab_free+0x32/0x70
kfree+0x11b/0x320
btrfs_rm_dev_replace_free_srcdev+0xca/0x280 [btrfs]
btrfs_dev_replace_finishing+0xd7e/0x14f0 [btrfs]
btrfs_dev_replace_by_ioctl+0x1286/0x25a0 [btrfs]
btrfs_ioctl+0xb27/0x57d0 [btrfs]
__x64_sys_ioctl+0x134/0x1b0
do_syscall_64+0x99/0x190
entry_SYSCALL_64_after_hwframe+0x6e/0x76
The buggy address belongs to the object at ffff8881543c8000
which belongs to the cache kmalloc-1k of size 1024
The buggy address is located 96 bytes inside of
freed 1024-byte region [ffff8881543c8000, ffff8881543c8400)
The buggy address belongs to the physical page:
page:00000000fe2c1285 refcount:1 mapcount:0 mapping:0000000000000000 index:0x0 pfn:0x1543c8
head:00000000fe2c1285 order:3 entire_mapcount:0 nr_pages_mapped:0 pincount:0
flags: 0x17ffffc0000840(slab|head|node=0|zone=2|lastcpupid=0x1fffff)
page_type: 0xffffffff()
raw: 0017ffffc0000840 ffff888100042dc0 ffffea0019e8f200 dead000000000002
raw: 0000000000000000 0000000000100010 00000001ffffffff 0000000000000000
page dumped because: kasan: bad access detected
Memory state around the buggy address:
ffff8881543c7f00: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
ffff8881543c7f80: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
>ffff8881543c8000: fa fb fb fb fb fb fb fb fb fb fb fb fb fb fb fb
^
ffff8881543c8080: fb fb fb fb fb fb fb fb fb fb fb fb fb fb fb fb
ffff8881543c8100: fb fb fb fb fb fb fb fb fb fb fb fb fb fb fb fb
这个释放后使用问题发生的原因是我们在do_zone_finish()中访问了一个已被移除的btrfs_device的过时区域信息。
事件序列如下:
btrfs_dev_replace_start
btrfs_scrub_dev
btrfs_dev_replace_finishing
btrfs_dev_replace_update_device_in_mapping_tree <-- 设备被替换
btrfs_rm_dev_replace_free_srcdev
btrfs_free_device <-- 设备被释放
cleaner_kthread
btrfs_delete_unused_bgs
btrfs_zone_finish
do_zone_finish <-- 引用了已释放的设备
出现此问题的原因是我们在使用一个
---截断---(CVE-2024-26944)
在Linux内核中,以下漏洞已被修复:
Bluetooth: HCI: 修复潜在的空指针解引用
修复hci_le_big_sync_established_evt()中潜在的空指针解引用问题。(CVE-2024-36011)
在Linux内核中,以下漏洞已被修复:
virtio_net: 修复napi_skb_cache_put警告
在提交bdacf3e34945 ("net: Use nested-BH locking for napi_alloc_cache.")合并后,开始出现以下警告:
WARNING: CPU: 5 PID: 1 at net/core/skbuff.c:1451 napi_skb_cache_put+0x82/0x4b0
__warn+0x12f/0x340
napi_skb_cache_put+0x82/0x4b0
napi_skb_cache_put+0x82/0x4b0
report_bug+0x165/0x370
handle_bug+0x3d/0x80
exc_invalid_op+0x1a/0x50
asm_exc_invalid_op+0x1a/0x20
__free_old_xmit+0x1c8/0x510
napi_skb_cache_put+0x82/0x4b0
__free_old_xmit+0x1c8/0x510
__free_old_xmit+0x1c8/0x510
__pfx___free_old_xmit+0x10/0x10
问题在于virtio假设它在NAPI上下文中运行,即使它不在(例如在netpoll情况下)。
为了解决这个问题,修改virtnet_poll_tx()仅在预算可用时设置NAPI。同样修改virtnet_poll_cleantx(),它总是假设它在NAPI上下文中。(CVE-2024-43835)
在Linux内核中,以下漏洞已被修复:
wifi: mac80211: 修复在启动tx ba会话时频段检查中的NULL解引用
在MLD连接中,link_data/link_conf是动态分配的。它们不指向vif->bss_conf。因此,vif->bss_conf将没有分配chanreq,然后chan将为NULL。调整代码以检查sta deflink上的ht_supported/vht_supported/has_he/has_eht。
cve名称 | 产品 | 组件 | 是否受影响 |
---|---|---|---|
CVE-2024-26944 | V6 | kernel | Fixed |
CVE-2024-36011 | V6 | kernel | Fixed |
CVE-2024-43835 | V6 | kernel | Fixed |
CVE-2024-43911 | V6 | kernel | Fixed |
CVE-2024-44989 | V6 | kernel | Fixed |
CVE-2024-45030 | V6 | kernel | Fixed |
CVE-2024-46678 | V6 | kernel | Fixed |
CVE-2024-46763 | V6 | kernel | Fixed |
CVE-2024-46783 | V6 | kernel | Fixed |
CVE-2024-46835 | V6 | kernel | Fixed |
CVE-2024-47666 | V6 | kernel | Fixed |
CVE-2024-47674 | V6 | kernel | Fixed |
CVE-2024-47723 | V6 | kernel | Fixed |
CVE-2024-47728 | V6 | kernel | Fixed |
CVE-2024-49945 | V6 | kernel | Fixed |
CVE-2024-50056 | V6 | kernel | Fixed |
CVE-2024-50061 | V6 | kernel | Fixed |
CVE-2024-50089 | V6 | kernel | Fixed |
CVE-2024-50099 | V6 | kernel | Fixed |
CVE-2024-50115 | V6 | kernel | Fixed |
CVE-2024-50124 | V6 | kernel | Fixed |
CVE-2024-50138 | V6 | kernel | Fixed |
CVE-2024-50151 | V6 | kernel | Fixed |
CVE-2024-50153 | V6 | kernel | Fixed |
CVE-2024-50180 | V6 | kernel | Fixed |
CVE-2024-50193 | V6 | kernel | Fixed |
CVE-2024-50198 | V6 | kernel | Fixed |
CVE-2024-50202 | V6 | kernel | Fixed |
CVE-2024-50215 | V6 | kernel | Fixed |
CVE-2024-50237 | V6 | kernel | Fixed |
CVE-2024-50242 | V6 | kernel | Fixed |
CVE-2024-50243 | V6 | kernel | Fixed |
CVE-2024-50244 | V6 | kernel | Fixed |
CVE-2024-50245 | V6 | kernel | Fixed |
CVE-2024-50246 | V6 | kernel | Fixed |
CVE-2024-50247 | V6 | kernel | Fixed |
CVE-2024-50250 | V6 | kernel | Fixed |
软件名称 | 架构 | 版本号 |
---|---|---|
bpftool | x86_64 | 7.2.0-1.ks6 |
kernel | x86_64 | 6.6.0-28.0.0.34.kb11.ks6 |
kernel-devel | x86_64 | 6.6.0-28.0.0.34.kb11.ks6 |
kernel-headers | x86_64 | 6.6.0-28.0.0.34.kb11.ks6 |
kernel-source | x86_64 | 6.6.0-28.0.0.34.kb11.ks6 |
kernel-tools | x86_64 | 6.6.0-28.0.0.34.kb11.ks6 |
kernel-tools-devel | x86_64 | 6.6.0-28.0.0.34.kb11.ks6 |
perf | x86_64 | 6.6.0-28.0.0.34.kb11.ks6 |
python3-perf | x86_64 | 6.6.0-28.0.0.34.kb11.ks6 |
bpftool | aarch64 | 7.2.0-1.ks6 |
kernel | aarch64 | 6.6.0-28.0.0.34.kb11.ks6 |
kernel-devel | aarch64 | 6.6.0-28.0.0.34.kb11.ks6 |
kernel-headers | aarch64 | 6.6.0-28.0.0.34.kb11.ks6 |
kernel-source | aarch64 | 6.6.0-28.0.0.34.kb11.ks6 |
kernel-tools | aarch64 | 6.6.0-28.0.0.34.kb11.ks6 |
kernel-tools-devel | aarch64 | 6.6.0-28.0.0.34.kb11.ks6 |
perf | aarch64 | 6.6.0-28.0.0.34.kb11.ks6 |
python3-perf | aarch64 | 6.6.0-28.0.0.34.kb11.ks6 |
方法一:下载安装包进行升级安装
1、通过下载链接下载需要升级的升级包保存,如 xxx.rpm
2、通过rpm命令升级,如 rpm -Uvh xxx.rpm
方法二:通过软件源进行升级安装
1、保持能够连接上互联网
2、通过yum命令升级指定的包,如 yum install 包名