kernel-5.14.0-570.42.2.el9_6
エラータID: AXSA:2025-10887:69
リリース日:
2025/09/22 Monday - 16:15
題名:
kernel-5.14.0-570.42.2.el9_6
影響のあるチャネル:
MIRACLE LINUX 9 for x86_64
Severity:
High
Description:
以下項目について対処しました。
[Security Fix]
- kernel の vkms ドライバには、メモリ領域の解放後利用、および
メモリ領域の二重解放の問題があるため、ローカルの攻撃者により、
情報の漏洩、データ破壊、およびサービス拒否攻撃を可能とする脆弱性が
存在します。(CVE-2025-22097)
- kernel の lpfc ドライバには、ローカルの攻撃者により、情報の漏洩、
データ破壊、およびサービス拒否攻撃を可能とする脆弱性が存在します。
(CVE-2025-38332)
- kernel のスケジューラの実装には、メモリ領域の解放後利用、
および競合状態に至る問題があるため、ローカルの攻撃者により、
特権昇格、およびサービス拒否攻撃 (クラッシュの発生) を可能と
する脆弱性が存在します。(CVE-2025-38352)
- kernel の DRM ドライバには、ローカルの攻撃者により、情報の
漏洩、データ破壊、およびサービス拒否攻撃を可能とする脆弱性が
存在します。(CVE-2025-38449)
解決策:
パッケージをアップデートしてください。
CVE:
CVE-2025-22097
In the Linux kernel, the following vulnerability has been resolved: drm/vkms: Fix use after free and double free on init error If the driver initialization fails, the vkms_exit() function might access an uninitialized or freed default_config pointer and it might double free it. Fix both possible errors by initializing default_config only when the driver initialization succeeded.
In the Linux kernel, the following vulnerability has been resolved: drm/vkms: Fix use after free and double free on init error If the driver initialization fails, the vkms_exit() function might access an uninitialized or freed default_config pointer and it might double free it. Fix both possible errors by initializing default_config only when the driver initialization succeeded.
CVE-2025-38332
In the Linux kernel, the following vulnerability has been resolved: scsi: lpfc: Use memcpy() for BIOS version The strlcat() with FORTIFY support is triggering a panic because it thinks the target buffer will overflow although the correct target buffer size is passed in. Anyway, instead of memset() with 0 followed by a strlcat(), just use memcpy() and ensure that the resulting buffer is NULL terminated. BIOSVersion is only used for the lpfc_printf_log() which expects a properly terminated string.
In the Linux kernel, the following vulnerability has been resolved: scsi: lpfc: Use memcpy() for BIOS version The strlcat() with FORTIFY support is triggering a panic because it thinks the target buffer will overflow although the correct target buffer size is passed in. Anyway, instead of memset() with 0 followed by a strlcat(), just use memcpy() and ensure that the resulting buffer is NULL terminated. BIOSVersion is only used for the lpfc_printf_log() which expects a properly terminated string.
CVE-2025-38352
In the Linux kernel, the following vulnerability has been resolved: posix-cpu-timers: fix race between handle_posix_cpu_timers() and posix_cpu_timer_del() If an exiting non-autoreaping task has already passed exit_notify() and calls handle_posix_cpu_timers() from IRQ, it can be reaped by its parent or debugger right after unlock_task_sighand(). If a concurrent posix_cpu_timer_del() runs at that moment, it won't be able to detect timer->it.cpu.firing != 0: cpu_timer_task_rcu() and/or lock_task_sighand() will fail. Add the tsk->exit_state check into run_posix_cpu_timers() to fix this. This fix is not needed if CONFIG_POSIX_CPU_TIMERS_TASK_WORK=y, because exit_task_work() is called before exit_notify(). But the check still makes sense, task_work_add(&tsk->posix_cputimers_work.work) will fail anyway in this case.
In the Linux kernel, the following vulnerability has been resolved: posix-cpu-timers: fix race between handle_posix_cpu_timers() and posix_cpu_timer_del() If an exiting non-autoreaping task has already passed exit_notify() and calls handle_posix_cpu_timers() from IRQ, it can be reaped by its parent or debugger right after unlock_task_sighand(). If a concurrent posix_cpu_timer_del() runs at that moment, it won't be able to detect timer->it.cpu.firing != 0: cpu_timer_task_rcu() and/or lock_task_sighand() will fail. Add the tsk->exit_state check into run_posix_cpu_timers() to fix this. This fix is not needed if CONFIG_POSIX_CPU_TIMERS_TASK_WORK=y, because exit_task_work() is called before exit_notify(). But the check still makes sense, task_work_add(&tsk->posix_cputimers_work.work) will fail anyway in this case.
CVE-2025-38449
In the Linux kernel, the following vulnerability has been resolved: drm/gem: Acquire references on GEM handles for framebuffers A GEM handle can be released while the GEM buffer object is attached to a DRM framebuffer. This leads to the release of the dma-buf backing the buffer object, if any. [1] Trying to use the framebuffer in further mode-setting operations leads to a segmentation fault. Most easily happens with driver that use shadow planes for vmap-ing the dma-buf during a page flip. An example is shown below. [ 156.791968] ------------[ cut here ]------------ [ 156.796830] WARNING: CPU: 2 PID: 2255 at drivers/dma-buf/dma-buf.c:1527 dma_buf_vmap+0x224/0x430 [...] [ 156.942028] RIP: 0010:dma_buf_vmap+0x224/0x430 [ 157.043420] Call Trace: [ 157.045898] [ 157.048030] ? show_trace_log_lvl+0x1af/0x2c0 [ 157.052436] ? show_trace_log_lvl+0x1af/0x2c0 [ 157.056836] ? show_trace_log_lvl+0x1af/0x2c0 [ 157.061253] ? drm_gem_shmem_vmap+0x74/0x710 [ 157.065567] ? dma_buf_vmap+0x224/0x430 [ 157.069446] ? __warn.cold+0x58/0xe4 [ 157.073061] ? dma_buf_vmap+0x224/0x430 [ 157.077111] ? report_bug+0x1dd/0x390 [ 157.080842] ? handle_bug+0x5e/0xa0 [ 157.084389] ? exc_invalid_op+0x14/0x50 [ 157.088291] ? asm_exc_invalid_op+0x16/0x20 [ 157.092548] ? dma_buf_vmap+0x224/0x430 [ 157.096663] ? dma_resv_get_singleton+0x6d/0x230 [ 157.101341] ? __pfx_dma_buf_vmap+0x10/0x10 [ 157.105588] ? __pfx_dma_resv_get_singleton+0x10/0x10 [ 157.110697] drm_gem_shmem_vmap+0x74/0x710 [ 157.114866] drm_gem_vmap+0xa9/0x1b0 [ 157.118763] drm_gem_vmap_unlocked+0x46/0xa0 [ 157.123086] drm_gem_fb_vmap+0xab/0x300 [ 157.126979] drm_atomic_helper_prepare_planes.part.0+0x487/0xb10 [ 157.133032] ? lockdep_init_map_type+0x19d/0x880 [ 157.137701] drm_atomic_helper_commit+0x13d/0x2e0 [ 157.142671] ? drm_atomic_nonblocking_commit+0xa0/0x180 [ 157.147988] drm_mode_atomic_ioctl+0x766/0xe40 [...] [ 157.346424] ---[ end trace 0000000000000000 ]--- Acquiring GEM handles for the framebuffer's GEM buffer objects prevents this from happening. The framebuffer's cleanup later puts the handle references. Commit 1a148af06000 ("drm/gem-shmem: Use dma_buf from GEM object instance") triggers the segmentation fault easily by using the dma-buf field more widely. The underlying issue with reference counting has been present before. v2: - acquire the handle instead of the BO (Christian) - fix comment style (Christian) - drop the Fixes tag (Christian) - rename err_ gotos - add missing Link tag
In the Linux kernel, the following vulnerability has been resolved: drm/gem: Acquire references on GEM handles for framebuffers A GEM handle can be released while the GEM buffer object is attached to a DRM framebuffer. This leads to the release of the dma-buf backing the buffer object, if any. [1] Trying to use the framebuffer in further mode-setting operations leads to a segmentation fault. Most easily happens with driver that use shadow planes for vmap-ing the dma-buf during a page flip. An example is shown below. [ 156.791968] ------------[ cut here ]------------ [ 156.796830] WARNING: CPU: 2 PID: 2255 at drivers/dma-buf/dma-buf.c:1527 dma_buf_vmap+0x224/0x430 [...] [ 156.942028] RIP: 0010:dma_buf_vmap+0x224/0x430 [ 157.043420] Call Trace: [ 157.045898]
追加情報:
N/A
ダウンロード:
SRPMS
- kernel-5.14.0-570.42.2.el9_6.src.rpm
MD5: 1810726a6208b0d7bbb7d8c493abe76a
SHA-256: 916bde12cb1bbcc2b294b1b5b9278449212a3f27db0d1bc7e4d5b561542e9e0f
Size: 142.55 MB
Asianux Server 9 for x86_64
- kernel-5.14.0-570.42.2.el9_6.x86_64.rpm
MD5: 6a7b059a8013463e6d634db05b541647
SHA-256: f038949b27129c17b961a6fd0f571df012d7ab89ddac5556d57865cb768f2632
Size: 1.80 MB - kernel-abi-stablelists-5.14.0-570.42.2.el9_6.noarch.rpm
MD5: 150e761858e81520fc8653337d093daf
SHA-256: 9446edda8007a793f386eede327b64f8c6fd7f62e24dc4a41e172d1980c271bf
Size: 1.82 MB - kernel-core-5.14.0-570.42.2.el9_6.x86_64.rpm
MD5: 578828785b5b94ee0522dd3bd6d8880f
SHA-256: 5409c776019dd2c147e289c31e2195491df3fadab92482948d042a4961fd8d9d
Size: 17.87 MB - kernel-cross-headers-5.14.0-570.42.2.el9_6.x86_64.rpm
MD5: c593aa83fd6f5385a212929f9ed1d4d6
SHA-256: ec75ddf7e0969ec2d4f15d25b0b967165b770d654259e0b06f7389b832201204
Size: 8.66 MB - kernel-debug-5.14.0-570.42.2.el9_6.x86_64.rpm
MD5: 53f7de642f12300799c6f64be92dc737
SHA-256: bea59fa906f827981cc333758caf25f7c9315d40546c043e86b17aef11f12d8f
Size: 1.80 MB - kernel-debug-core-5.14.0-570.42.2.el9_6.x86_64.rpm
MD5: af78949d2d39411d585af9b4e904692a
SHA-256: 5ad368b3874bd5a65e7c98948ccd4971d3d0cd1ef6379cf3a4cc5e96f193cdde
Size: 31.31 MB - kernel-debug-devel-5.14.0-570.42.2.el9_6.x86_64.rpm
MD5: b23d04d7c8be5a7df429189108b5dd00
SHA-256: 448715636f7bf5efbc7217447f7aa121d48c213ea8071a3529ffe57f14b49323
Size: 21.79 MB - kernel-debug-devel-matched-5.14.0-570.42.2.el9_6.x86_64.rpm
MD5: 44f511cbe7e4de6f79fd38e7d215cd12
SHA-256: e20f5c4e936b4e028d9917245c6d61879d8251123b2adace45036d8c0db02500
Size: 1.80 MB - kernel-debug-modules-5.14.0-570.42.2.el9_6.x86_64.rpm
MD5: 4505416bc505900e1118ac98c92de6b1
SHA-256: e8cee3e7840a1e7a16ace70b50184247620899d4bb4f6213e13fc49057b35ed2
Size: 67.37 MB - kernel-debug-modules-core-5.14.0-570.42.2.el9_6.x86_64.rpm
MD5: c7700b0e6e7e011a67dcf4cb8aa9630b
SHA-256: 22cb33efb571381967235cf990cba8aa086f41cfff72b74e9975d5577214915c
Size: 48.92 MB - kernel-debug-modules-extra-5.14.0-570.42.2.el9_6.x86_64.rpm
MD5: f168fcf6b283544591c7b3874c118e26
SHA-256: 24c6d77538707df6c8110309bc2e66261a70184777b082939e167c4dd443fdcc
Size: 2.57 MB - kernel-debug-uki-virt-5.14.0-570.42.2.el9_6.x86_64.rpm
MD5: 7aa12b06d8dfbfd202ed339796d48659
SHA-256: f2268699067d49ebd377c997112dba45910211d5d6ea8954ab599c65b1da78ba
Size: 84.38 MB - kernel-devel-5.14.0-570.42.2.el9_6.x86_64.rpm
MD5: 604a9d8474e43d5b599eb4bec6e41008
SHA-256: 03423e3c610d70bcf696447483c8e853baa807b91d9d129c200c32c4f1bfd056
Size: 21.62 MB - kernel-devel-matched-5.14.0-570.42.2.el9_6.x86_64.rpm
MD5: 625eeea0c15a0149e0eabdbdfa5554b1
SHA-256: 3d0e42da379ae8f17c2b9919bde986ee5c1e48d52c5bf5669efc7ccced7f2164
Size: 1.80 MB - kernel-doc-5.14.0-570.42.2.el9_6.noarch.rpm
MD5: 57445e3168646e394febd015ca2d9e7a
SHA-256: fa3b891d17908b31408bbab25c3687782e78c99d0a3fb2ae20424d1dc900380a
Size: 37.95 MB - kernel-headers-5.14.0-570.42.2.el9_6.x86_64.rpm
MD5: 0726cc0666250ae57f8e1e92efe02eb1
SHA-256: e39a8cdd8d08bf615b01695f3117c174d586bb857aef6c89b354dc5952911063
Size: 3.54 MB - kernel-modules-5.14.0-570.42.2.el9_6.x86_64.rpm
MD5: 3f1114eae5ea97ff248f94a7def63283
SHA-256: cc885942af1f6ea5c5b321a5fd025a64026f2d500569c88b119b973b89e360fc
Size: 38.99 MB - kernel-modules-core-5.14.0-570.42.2.el9_6.x86_64.rpm
MD5: 5010b58679225f8d5bc66dae759e2581
SHA-256: 8d2b279234c9a5bf01726956cfda8918282efcb1e3d03827d9047f85e54d5003
Size: 30.90 MB - kernel-modules-extra-5.14.0-570.42.2.el9_6.x86_64.rpm
MD5: 13e10182c9985b8e6a80adc846adf82b
SHA-256: 5e97f8657bee492b8262f34c9c97313a443e949679a3641082d679f92723f9a3
Size: 2.22 MB - kernel-rt-5.14.0-570.42.2.el9_6.x86_64.rpm
MD5: ff88572bf53ac45f575d824192143d10
SHA-256: 6c08b00bc0c8c4bd80dbd065d4d262356e0750423b945cb2a6071e270db19900
Size: 1.80 MB - kernel-rt-core-5.14.0-570.42.2.el9_6.x86_64.rpm
MD5: 689812411f4510cdd9948fa9602e1f6f
SHA-256: a07f56413fd12daca1afbe1735aa4d6f255be8234948f6e58e2050579d9311ab
Size: 17.77 MB - kernel-rt-debug-5.14.0-570.42.2.el9_6.x86_64.rpm
MD5: 317906c69a9b201a0e0f3767e769c6e5
SHA-256: cb858e7a663d56a34a59e859105a7d33140b66febb8a64d221d8b6602fc84fc9
Size: 1.80 MB - kernel-rt-debug-core-5.14.0-570.42.2.el9_6.x86_64.rpm
MD5: f32bb9ea8cf6de33708e1b9b237e8592
SHA-256: e13eede68375befd199093bb5ef045e74483ba69001d814ae35d906c14f5f3f4
Size: 19.17 MB - kernel-rt-debug-devel-5.14.0-570.42.2.el9_6.x86_64.rpm
MD5: d4ad2b831a9a0f834b1e7eb2a02b3543
SHA-256: c1028973a7bfb6e8de60e070a61be921649b01d04b405c60fd56714bb6698d34
Size: 21.75 MB - kernel-rt-debug-modules-5.14.0-570.42.2.el9_6.x86_64.rpm
MD5: 12c7024c7c815097e88cb001680ce8ec
SHA-256: aedda94cd49d55cd773efd7624f662de9df2fe100a6c52fdcff6b69634950a0e
Size: 40.38 MB - kernel-rt-debug-modules-core-5.14.0-570.42.2.el9_6.x86_64.rpm
MD5: e9a5032feba58b6290d5409ab922dd80
SHA-256: 353cc8a60cad1689f18253acfb3853f0e9bf2493d18d69eb6f8d249417b714dd
Size: 31.32 MB - kernel-rt-debug-modules-extra-5.14.0-570.42.2.el9_6.x86_64.rpm
MD5: 4f99aa2282b850046ba08e2d2e98489a
SHA-256: afe3d1c0d6180ec70a8eec4e5d8bc20f9a0cd84eba5ec717841c3cd600b36d41
Size: 2.25 MB - kernel-rt-devel-5.14.0-570.42.2.el9_6.x86_64.rpm
MD5: 207a157e9e5fef02d6c02df2a6f50d66
SHA-256: ac599fd5f73dbfecafe97442834ad93cedeace181307605ed87b20adca8883f0
Size: 21.60 MB - kernel-rt-modules-5.14.0-570.42.2.el9_6.x86_64.rpm
MD5: e1dd51107e754699e1d4ee3f4a65290b
SHA-256: 210518da8e383fed66f1a82dd50bc8adedd2fbf0ee91d9c409ab716c0166e65e
Size: 38.99 MB - kernel-rt-modules-core-5.14.0-570.42.2.el9_6.x86_64.rpm
MD5: c4a43c5787cb7653e0efbbde3280bfa3
SHA-256: 336f3d1d1f2d1f781f2b1b0194c13e564f3d1638df234d47fc970c44a54eb6f0
Size: 30.28 MB - kernel-rt-modules-extra-5.14.0-570.42.2.el9_6.x86_64.rpm
MD5: 7719f9fcf1b489b62efe2da2004dc931
SHA-256: f914ef1e3052095ef44b6b89c4363b7a67a21e9e35dcaf0e438b4b73a726608d
Size: 2.22 MB - kernel-tools-5.14.0-570.42.2.el9_6.x86_64.rpm
MD5: 327c2707e94f04fc25e52b528bde4f98
SHA-256: f762e276a19b34a74bf99711a548175a88052a7af9d28344757ff2f1a097b731
Size: 2.08 MB - kernel-tools-libs-5.14.0-570.42.2.el9_6.x86_64.rpm
MD5: 2871de41da90cc5191b1fccdd663fb90
SHA-256: cc4d47bc34eeb4b2007bf0c77165741bea5b61dcb4b15b65fdd851de95b9a74c
Size: 1.81 MB - kernel-tools-libs-devel-5.14.0-570.42.2.el9_6.x86_64.rpm
MD5: b43a279c0e441c55591a6c9748485c90
SHA-256: ffde1a65b9252227bfad9bedbd5da1edf58b7e27266a36a44e3dfc7d2345b1af
Size: 1.80 MB - kernel-uki-virt-5.14.0-570.42.2.el9_6.x86_64.rpm
MD5: a2908b6b6ab909d747c1c4bb29ee9818
SHA-256: 4cc6ac7edea6aa10803dc1e4cd3cc211785150fbd1f70913e3368b3d367fa4b8
Size: 63.01 MB - kernel-uki-virt-addons-5.14.0-570.42.2.el9_6.x86_64.rpm
MD5: c94afca0f229ea9d1620335308fcf4e9
SHA-256: d2fee4cdb0dc45a8856906f456ec551b0c75e03f927d2b3745c4e7e230ba5364
Size: 1.82 MB - libperf-5.14.0-570.42.2.el9_6.x86_64.rpm
MD5: b117f9a062b316c8e6c7c459fd0073b6
SHA-256: bab36d7ffd17f22088c2bdb34eec55fa88d7a1c23b7121bb70e990b87f520e07
Size: 1.82 MB - perf-5.14.0-570.42.2.el9_6.x86_64.rpm
MD5: 4d7db33b30bb9a14d0650a327a677553
SHA-256: 8ead8befbc344b61fe69517e032997c621dadf6ba5b321c4e5aa7b649ff22f05
Size: 4.03 MB - python3-perf-5.14.0-570.42.2.el9_6.x86_64.rpm
MD5: 2c6fcb3c6cefca19ff8e792d0b36e1f6
SHA-256: 005de3d9256f26e011e2c92fb0d7349fcb9a8d47224bb7060939476a960b7b3e
Size: 3.21 MB - rtla-5.14.0-570.42.2.el9_6.x86_64.rpm
MD5: 38230711db7092bd68728d524d6ca7ae
SHA-256: 0b31d6b6dbf5441aa353aadbbed8f6109f2647986a7ba6b46552ead707161541
Size: 1.86 MB - rv-5.14.0-570.42.2.el9_6.x86_64.rpm
MD5: 5947484dfac60aeaa0007a592ce5e8d8
SHA-256: 2b9a1190b5034a13460395d3cb8397c2b70678e958392dff02d807b7679e3d9b
Size: 1.81 MB