3735 lines
159 KiB
XML
3735 lines
159 KiB
XML
<?xml version="1.0" encoding="UTF-8"?>
|
|
<cvrfdoc xmlns="http://www.icasi.org/CVRF/schema/cvrf/1.1" xmlns:cvrf="http://www.icasi.org/CVRF/schema/cvrf/1.1">
|
|
<DocumentTitle xml:lang="en">An update for kernel is now available for openEuler-20.03-LTS-SP4</DocumentTitle>
|
|
<DocumentType>Security Advisory</DocumentType>
|
|
<DocumentPublisher Type="Vendor">
|
|
<ContactDetails>openeuler-security@openeuler.org</ContactDetails>
|
|
<IssuingAuthority>openEuler security committee</IssuingAuthority>
|
|
</DocumentPublisher>
|
|
<DocumentTracking>
|
|
<Identification>
|
|
<ID>openEuler-SA-2024-1484</ID>
|
|
</Identification>
|
|
<Status>Final</Status>
|
|
<Version>1.0</Version>
|
|
<RevisionHistory>
|
|
<Revision>
|
|
<Number>1.0</Number>
|
|
<Date>2024-04-19</Date>
|
|
<Description>Initial</Description>
|
|
</Revision>
|
|
</RevisionHistory>
|
|
<InitialReleaseDate>2024-04-19</InitialReleaseDate>
|
|
<CurrentReleaseDate>2024-04-19</CurrentReleaseDate>
|
|
<Generator>
|
|
<Engine>openEuler SA Tool V1.0</Engine>
|
|
<Date>2024-04-19</Date>
|
|
</Generator>
|
|
</DocumentTracking>
|
|
<DocumentNotes>
|
|
<Note Title="Synopsis" Type="General" Ordinal="1" xml:lang="en">kernel security update</Note>
|
|
<Note Title="Summary" Type="General" Ordinal="2" xml:lang="en">An update for kernel is now available for openEuler-20.03-LTS-SP4.</Note>
|
|
<Note Title="Description" Type="General" Ordinal="3" xml:lang="en">The Linux Kernel, the operating system core itself.
|
|
|
|
Security Fix(es):
|
|
|
|
In the Linux kernel, the following vulnerability has been resolved:
|
|
|
|
i2c: img-scb: fix reference leak when pm_runtime_get_sync fails
|
|
|
|
The PM reference count is not expected to be incremented on
|
|
return in functions img_i2c_xfer and img_i2c_init.
|
|
|
|
However, pm_runtime_get_sync will increment the PM reference
|
|
count even failed. Forgetting to putting operation will result
|
|
in a reference leak here.
|
|
|
|
Replace it with pm_runtime_resume_and_get to keep usage
|
|
counter balanced.(CVE-2020-36783)
|
|
|
|
In the Linux kernel, the following vulnerability has been resolved:
|
|
|
|
kyber: fix out of bounds access when preempted
|
|
|
|
__blk_mq_sched_bio_merge() gets the ctx and hctx for the current CPU and
|
|
passes the hctx to ->bio_merge(). kyber_bio_merge() then gets the ctx
|
|
for the current CPU again and uses that to get the corresponding Kyber
|
|
context in the passed hctx. However, the thread may be preempted between
|
|
the two calls to blk_mq_get_ctx(), and the ctx returned the second time
|
|
may no longer correspond to the passed hctx. This "works" accidentally
|
|
most of the time, but it can cause us to read garbage if the second ctx
|
|
came from an hctx with more ctx's than the first one (i.e., if
|
|
ctx->index_hw[hctx->type] > hctx->nr_ctx).
|
|
|
|
This manifested as this UBSAN array index out of bounds error reported
|
|
by Jakub:
|
|
|
|
UBSAN: array-index-out-of-bounds in ../kernel/locking/qspinlock.c:130:9
|
|
index 13106 is out of range for type 'long unsigned int [128]'
|
|
Call Trace:
|
|
dump_stack+0xa4/0xe5
|
|
ubsan_epilogue+0x5/0x40
|
|
__ubsan_handle_out_of_bounds.cold.13+0x2a/0x34
|
|
queued_spin_lock_slowpath+0x476/0x480
|
|
do_raw_spin_lock+0x1c2/0x1d0
|
|
kyber_bio_merge+0x112/0x180
|
|
blk_mq_submit_bio+0x1f5/0x1100
|
|
submit_bio_noacct+0x7b0/0x870
|
|
submit_bio+0xc2/0x3a0
|
|
btrfs_map_bio+0x4f0/0x9d0
|
|
btrfs_submit_data_bio+0x24e/0x310
|
|
submit_one_bio+0x7f/0xb0
|
|
submit_extent_page+0xc4/0x440
|
|
__extent_writepage_io+0x2b8/0x5e0
|
|
__extent_writepage+0x28d/0x6e0
|
|
extent_write_cache_pages+0x4d7/0x7a0
|
|
extent_writepages+0xa2/0x110
|
|
do_writepages+0x8f/0x180
|
|
__writeback_single_inode+0x99/0x7f0
|
|
writeback_sb_inodes+0x34e/0x790
|
|
__writeback_inodes_wb+0x9e/0x120
|
|
wb_writeback+0x4d2/0x660
|
|
wb_workfn+0x64d/0xa10
|
|
process_one_work+0x53a/0xa80
|
|
worker_thread+0x69/0x5b0
|
|
kthread+0x20b/0x240
|
|
ret_from_fork+0x1f/0x30
|
|
|
|
Only Kyber uses the hctx, so fix it by passing the request_queue to
|
|
->bio_merge() instead. BFQ and mq-deadline just use that, and Kyber can
|
|
map the queues itself to avoid the mismatch.(CVE-2021-46984)
|
|
|
|
In the Linux kernel, the following vulnerability has been resolved:
|
|
|
|
bus: qcom: Put child node before return
|
|
|
|
Put child node before return to fix potential reference count leak.
|
|
Generally, the reference count of child is incremented and decremented
|
|
automatically in the macro for_each_available_child_of_node() and should
|
|
be decremented manually if the loop is broken in loop body.(CVE-2021-47054)
|
|
|
|
In the Linux kernel, the following vulnerability has been resolved:
|
|
|
|
crypto: qat - ADF_STATUS_PF_RUNNING should be set after adf_dev_init
|
|
|
|
ADF_STATUS_PF_RUNNING is (only) used and checked by adf_vf2pf_shutdown()
|
|
before calling adf_iov_putmsg()->mutex_lock(vf2pf_lock), however the
|
|
vf2pf_lock is initialized in adf_dev_init(), which can fail and when it
|
|
fail, the vf2pf_lock is either not initialized or destroyed, a subsequent
|
|
use of vf2pf_lock will cause issue.
|
|
To fix this issue, only set this flag if adf_dev_init() returns 0.
|
|
|
|
[ 7.178404] BUG: KASAN: user-memory-access in __mutex_lock.isra.0+0x1ac/0x7c0
|
|
[ 7.180345] Call Trace:
|
|
[ 7.182576] mutex_lock+0xc9/0xd0
|
|
[ 7.183257] adf_iov_putmsg+0x118/0x1a0 [intel_qat]
|
|
[ 7.183541] adf_vf2pf_shutdown+0x4d/0x7b [intel_qat]
|
|
[ 7.183834] adf_dev_shutdown+0x172/0x2b0 [intel_qat]
|
|
[ 7.184127] adf_probe+0x5e9/0x600 [qat_dh895xccvf](CVE-2021-47056)
|
|
|
|
In the Linux kernel, the following vulnerability has been resolved:
|
|
|
|
KVM: Stop looking for coalesced MMIO zones if the bus is destroyed
|
|
|
|
Abort the walk of coalesced MMIO zones if kvm_io_bus_unregister_dev()
|
|
fails to allocate memory for the new instance of the bus. If it can't
|
|
instantiate a new bus, unregister_dev() destroys all devices _except_ the
|
|
target device. But, it doesn't tell the caller that it obliterated the
|
|
bus and invoked the destructor for all devices that were on the bus. In
|
|
the coalesced MMIO case, this can result in a deleted list entry
|
|
dereference due to attempting to continue iterating on coalesced_zones
|
|
after future entries (in the walk) have been deleted.
|
|
|
|
Opportunistically add curly braces to the for-loop, which encompasses
|
|
many lines but sneaks by without braces due to the guts being a single
|
|
if statement.(CVE-2021-47060)
|
|
|
|
In the Linux kernel, the following vulnerability has been resolved:
|
|
|
|
KVM: Destroy I/O bus devices on unregister failure _after_ sync'ing SRCU
|
|
|
|
If allocating a new instance of an I/O bus fails when unregistering a
|
|
device, wait to destroy the device until after all readers are guaranteed
|
|
to see the new null bus. Destroying devices before the bus is nullified
|
|
could lead to use-after-free since readers expect the devices on their
|
|
reference of the bus to remain valid.(CVE-2021-47061)
|
|
|
|
In the Linux kernel, the following vulnerability has been resolved:
|
|
|
|
drm: bridge/panel: Cleanup connector on bridge detach
|
|
|
|
If we don't call drm_connector_cleanup() manually in
|
|
panel_bridge_detach(), the connector will be cleaned up with the other
|
|
DRM objects in the call to drm_mode_config_cleanup(). However, since our
|
|
drm_connector is devm-allocated, by the time drm_mode_config_cleanup()
|
|
will be called, our connector will be long gone. Therefore, the
|
|
connector must be cleaned up when the bridge is detached to avoid
|
|
use-after-free conditions.
|
|
|
|
v2: Cleanup connector only if it was created
|
|
|
|
v3: Add FIXME
|
|
|
|
v4: (Use connector->dev) directly in if() block(CVE-2021-47063)
|
|
|
|
In the Linux kernel, the following vulnerability has been resolved:
|
|
|
|
uio_hv_generic: Fix a memory leak in error handling paths
|
|
|
|
If 'vmbus_establish_gpadl()' fails, the (recv|send)_gpadl will not be
|
|
updated and 'hv_uio_cleanup()' in the error handling path will not be
|
|
able to free the corresponding buffer.
|
|
|
|
In such a case, we need to free the buffer explicitly.(CVE-2021-47071)
|
|
|
|
In the Linux kernel, the following vulnerability has been resolved:
|
|
|
|
nvme-loop: fix memory leak in nvme_loop_create_ctrl()
|
|
|
|
When creating loop ctrl in nvme_loop_create_ctrl(), if nvme_init_ctrl()
|
|
fails, the loop ctrl should be freed before jumping to the "out" label.(CVE-2021-47074)
|
|
|
|
In the Linux kernel, the following vulnerability has been resolved:
|
|
|
|
scsi: qedf: Add pointer checks in qedf_update_link_speed()
|
|
|
|
The following trace was observed:
|
|
|
|
[ 14.042059] Call Trace:
|
|
[ 14.042061] <IRQ>
|
|
[ 14.042068] qedf_link_update+0x144/0x1f0 [qedf]
|
|
[ 14.042117] qed_link_update+0x5c/0x80 [qed]
|
|
[ 14.042135] qed_mcp_handle_link_change+0x2d2/0x410 [qed]
|
|
[ 14.042155] ? qed_set_ptt+0x70/0x80 [qed]
|
|
[ 14.042170] ? qed_set_ptt+0x70/0x80 [qed]
|
|
[ 14.042186] ? qed_rd+0x13/0x40 [qed]
|
|
[ 14.042205] qed_mcp_handle_events+0x437/0x690 [qed]
|
|
[ 14.042221] ? qed_set_ptt+0x70/0x80 [qed]
|
|
[ 14.042239] qed_int_sp_dpc+0x3a6/0x3e0 [qed]
|
|
[ 14.042245] tasklet_action_common.isra.14+0x5a/0x100
|
|
[ 14.042250] __do_softirq+0xe4/0x2f8
|
|
[ 14.042253] irq_exit+0xf7/0x100
|
|
[ 14.042255] do_IRQ+0x7f/0xd0
|
|
[ 14.042257] common_interrupt+0xf/0xf
|
|
[ 14.042259] </IRQ>
|
|
|
|
API qedf_link_update() is getting called from QED but by that time
|
|
shost_data is not initialised. This results in a NULL pointer dereference
|
|
when we try to dereference shost_data while updating supported_speeds.
|
|
|
|
Add a NULL pointer check before dereferencing shost_data.(CVE-2021-47077)
|
|
|
|
In the Linux kernel, the following vulnerability has been resolved:
|
|
|
|
RDMA/rxe: Clear all QP fields if creation failed
|
|
|
|
rxe_qp_do_cleanup() relies on valid pointer values in QP for the properly
|
|
created ones, but in case rxe_qp_from_init() failed it was filled with
|
|
garbage and caused tot the following error.
|
|
|
|
refcount_t: underflow; use-after-free.
|
|
WARNING: CPU: 1 PID: 12560 at lib/refcount.c:28 refcount_warn_saturate+0x1d1/0x1e0 lib/refcount.c:28
|
|
Modules linked in:
|
|
CPU: 1 PID: 12560 Comm: syz-executor.4 Not tainted 5.12.0-syzkaller #0
|
|
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 01/01/2011
|
|
RIP: 0010:refcount_warn_saturate+0x1d1/0x1e0 lib/refcount.c:28
|
|
Code: e9 db fe ff ff 48 89 df e8 2c c2 ea fd e9 8a fe ff ff e8 72 6a a7 fd 48 c7 c7 e0 b2 c1 89 c6 05 dc 3a e6 09 01 e8 ee 74 fb 04 <0f> 0b e9 af fe ff ff 0f 1f 84 00 00 00 00 00 41 56 41 55 41 54 55
|
|
RSP: 0018:ffffc900097ceba8 EFLAGS: 00010286
|
|
RAX: 0000000000000000 RBX: 0000000000000000 RCX: 0000000000000000
|
|
RDX: 0000000000040000 RSI: ffffffff815bb075 RDI: fffff520012f9d67
|
|
RBP: 0000000000000003 R08: 0000000000000000 R09: 0000000000000000
|
|
R10: ffffffff815b4eae R11: 0000000000000000 R12: ffff8880322a4800
|
|
R13: ffff8880322a4940 R14: ffff888033044e00 R15: 0000000000000000
|
|
FS: 00007f6eb2be3700(0000) GS:ffff8880b9d00000(0000) knlGS:0000000000000000
|
|
CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
|
|
CR2: 00007fdbe5d41000 CR3: 000000001d181000 CR4: 00000000001506e0
|
|
DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000
|
|
DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400
|
|
Call Trace:
|
|
__refcount_sub_and_test include/linux/refcount.h:283 [inline]
|
|
__refcount_dec_and_test include/linux/refcount.h:315 [inline]
|
|
refcount_dec_and_test include/linux/refcount.h:333 [inline]
|
|
kref_put include/linux/kref.h:64 [inline]
|
|
rxe_qp_do_cleanup+0x96f/0xaf0 drivers/infiniband/sw/rxe/rxe_qp.c:805
|
|
execute_in_process_context+0x37/0x150 kernel/workqueue.c:3327
|
|
rxe_elem_release+0x9f/0x180 drivers/infiniband/sw/rxe/rxe_pool.c:391
|
|
kref_put include/linux/kref.h:65 [inline]
|
|
rxe_create_qp+0x2cd/0x310 drivers/infiniband/sw/rxe/rxe_verbs.c:425
|
|
_ib_create_qp drivers/infiniband/core/core_priv.h:331 [inline]
|
|
ib_create_named_qp+0x2ad/0x1370 drivers/infiniband/core/verbs.c:1231
|
|
ib_create_qp include/rdma/ib_verbs.h:3644 [inline]
|
|
create_mad_qp+0x177/0x2d0 drivers/infiniband/core/mad.c:2920
|
|
ib_mad_port_open drivers/infiniband/core/mad.c:3001 [inline]
|
|
ib_mad_init_device+0xd6f/0x1400 drivers/infiniband/core/mad.c:3092
|
|
add_client_context+0x405/0x5e0 drivers/infiniband/core/device.c:717
|
|
enable_device_and_get+0x1cd/0x3b0 drivers/infiniband/core/device.c:1331
|
|
ib_register_device drivers/infiniband/core/device.c:1413 [inline]
|
|
ib_register_device+0x7c7/0xa50 drivers/infiniband/core/device.c:1365
|
|
rxe_register_device+0x3d5/0x4a0 drivers/infiniband/sw/rxe/rxe_verbs.c:1147
|
|
rxe_add+0x12fe/0x16d0 drivers/infiniband/sw/rxe/rxe.c:247
|
|
rxe_net_add+0x8c/0xe0 drivers/infiniband/sw/rxe/rxe_net.c:503
|
|
rxe_newlink drivers/infiniband/sw/rxe/rxe.c:269 [inline]
|
|
rxe_newlink+0xb7/0xe0 drivers/infiniband/sw/rxe/rxe.c:250
|
|
nldev_newlink+0x30e/0x550 drivers/infiniband/core/nldev.c:1555
|
|
rdma_nl_rcv_msg+0x36d/0x690 drivers/infiniband/core/netlink.c:195
|
|
rdma_nl_rcv_skb drivers/infiniband/core/netlink.c:239 [inline]
|
|
rdma_nl_rcv+0x2ee/0x430 drivers/infiniband/core/netlink.c:259
|
|
netlink_unicast_kernel net/netlink/af_netlink.c:1312 [inline]
|
|
netlink_unicast+0x533/0x7d0 net/netlink/af_netlink.c:1338
|
|
netlink_sendmsg+0x856/0xd90 net/netlink/af_netlink.c:1927
|
|
sock_sendmsg_nosec net/socket.c:654 [inline]
|
|
sock_sendmsg+0xcf/0x120 net/socket.c:674
|
|
____sys_sendmsg+0x6e8/0x810 net/socket.c:2350
|
|
___sys_sendmsg+0xf3/0x170 net/socket.c:2404
|
|
__sys_sendmsg+0xe5/0x1b0 net/socket.c:2433
|
|
do_syscall_64+0x3a/0xb0 arch/x86/entry/common.c:47
|
|
entry_SYSCALL_64_after_hwframe+0
|
|
---truncated---(CVE-2021-47078)
|
|
|
|
In the Linux kernel, the following vulnerability has been resolved:
|
|
|
|
asix: fix uninit-value in asix_mdio_read()
|
|
|
|
asix_read_cmd() may read less than sizeof(smsr) bytes and in this case
|
|
smsr will be uninitialized.
|
|
|
|
Fail log:
|
|
BUG: KMSAN: uninit-value in asix_check_host_enable drivers/net/usb/asix_common.c:82 [inline]
|
|
BUG: KMSAN: uninit-value in asix_check_host_enable drivers/net/usb/asix_common.c:82 [inline] drivers/net/usb/asix_common.c:497
|
|
BUG: KMSAN: uninit-value in asix_mdio_read+0x3c1/0xb00 drivers/net/usb/asix_common.c:497 drivers/net/usb/asix_common.c:497
|
|
asix_check_host_enable drivers/net/usb/asix_common.c:82 [inline]
|
|
asix_check_host_enable drivers/net/usb/asix_common.c:82 [inline] drivers/net/usb/asix_common.c:497
|
|
asix_mdio_read+0x3c1/0xb00 drivers/net/usb/asix_common.c:497 drivers/net/usb/asix_common.c:497(CVE-2021-47101)
|
|
|
|
In the Linux kernel, the following vulnerability has been resolved:
|
|
|
|
net/tls: Fix use-after-free after the TLS device goes down and up
|
|
|
|
When a netdev with active TLS offload goes down, tls_device_down is
|
|
called to stop the offload and tear down the TLS context. However, the
|
|
socket stays alive, and it still points to the TLS context, which is now
|
|
deallocated. If a netdev goes up, while the connection is still active,
|
|
and the data flow resumes after a number of TCP retransmissions, it will
|
|
lead to a use-after-free of the TLS context.
|
|
|
|
This commit addresses this bug by keeping the context alive until its
|
|
normal destruction, and implements the necessary fallbacks, so that the
|
|
connection can resume in software (non-offloaded) kTLS mode.
|
|
|
|
On the TX side tls_sw_fallback is used to encrypt all packets. The RX
|
|
side already has all the necessary fallbacks, because receiving
|
|
non-decrypted packets is supported. The thing needed on the RX side is
|
|
to block resync requests, which are normally produced after receiving
|
|
non-decrypted packets.
|
|
|
|
The necessary synchronization is implemented for a graceful teardown:
|
|
first the fallbacks are deployed, then the driver resources are released
|
|
(it used to be possible to have a tls_dev_resync after tls_dev_del).
|
|
|
|
A new flag called TLS_RX_DEV_DEGRADED is added to indicate the fallback
|
|
mode. It's used to skip the RX resync logic completely, as it becomes
|
|
useless, and some objects may be released (for example, resync_async,
|
|
which is allocated and freed by the driver).(CVE-2021-47131)
|
|
|
|
In the Linux kernel, the following vulnerability has been resolved:
|
|
|
|
drm/amdgpu: Fix a use-after-free
|
|
|
|
looks like we forget to set ttm->sg to NULL.
|
|
Hit panic below
|
|
|
|
[ 1235.844104] general protection fault, probably for non-canonical address 0x6b6b6b6b6b6b7b4b: 0000 [#1] SMP DEBUG_PAGEALLOC NOPTI
|
|
[ 1235.989074] Call Trace:
|
|
[ 1235.991751] sg_free_table+0x17/0x20
|
|
[ 1235.995667] amdgpu_ttm_backend_unbind.cold+0x4d/0xf7 [amdgpu]
|
|
[ 1236.002288] amdgpu_ttm_backend_destroy+0x29/0x130 [amdgpu]
|
|
[ 1236.008464] ttm_tt_destroy+0x1e/0x30 [ttm]
|
|
[ 1236.013066] ttm_bo_cleanup_memtype_use+0x51/0xa0 [ttm]
|
|
[ 1236.018783] ttm_bo_release+0x262/0xa50 [ttm]
|
|
[ 1236.023547] ttm_bo_put+0x82/0xd0 [ttm]
|
|
[ 1236.027766] amdgpu_bo_unref+0x26/0x50 [amdgpu]
|
|
[ 1236.032809] amdgpu_amdkfd_gpuvm_alloc_memory_of_gpu+0x7aa/0xd90 [amdgpu]
|
|
[ 1236.040400] kfd_ioctl_alloc_memory_of_gpu+0xe2/0x330 [amdgpu]
|
|
[ 1236.046912] kfd_ioctl+0x463/0x690 [amdgpu](CVE-2021-47142)
|
|
|
|
In the Linux kernel, the following vulnerability has been resolved:
|
|
|
|
net/smc: remove device from smcd_dev_list after failed device_add()
|
|
|
|
If the device_add() for a smcd_dev fails, there's no cleanup step that
|
|
rolls back the earlier list_add(). The device subsequently gets freed,
|
|
and we end up with a corrupted list.
|
|
|
|
Add some error handling that removes the device from the list.(CVE-2021-47143)
|
|
|
|
In the Linux kernel, the following vulnerability has been resolved:
|
|
|
|
drm/amd/amdgpu: fix refcount leak
|
|
|
|
[Why]
|
|
the gem object rfb->base.obj[0] is get according to num_planes
|
|
in amdgpufb_create, but is not put according to num_planes
|
|
|
|
[How]
|
|
put rfb->base.obj[0] in amdgpu_fbdev_destroy according to num_planes(CVE-2021-47144)
|
|
|
|
In the Linux kernel, the following vulnerability has been resolved:
|
|
|
|
btrfs: do not BUG_ON in link_to_fixup_dir
|
|
|
|
While doing error injection testing I got the following panic
|
|
|
|
kernel BUG at fs/btrfs/tree-log.c:1862!
|
|
invalid opcode: 0000 [#1] SMP NOPTI
|
|
CPU: 1 PID: 7836 Comm: mount Not tainted 5.13.0-rc1+ #305
|
|
Hardware name: QEMU Standard PC (Q35 + ICH9, 2009), BIOS 1.13.0-2.fc32 04/01/2014
|
|
RIP: 0010:link_to_fixup_dir+0xd5/0xe0
|
|
RSP: 0018:ffffb5800180fa30 EFLAGS: 00010216
|
|
RAX: fffffffffffffffb RBX: 00000000fffffffb RCX: ffff8f595287faf0
|
|
RDX: ffffb5800180fa37 RSI: ffff8f5954978800 RDI: 0000000000000000
|
|
RBP: ffff8f5953af9450 R08: 0000000000000019 R09: 0000000000000001
|
|
R10: 000151f408682970 R11: 0000000120021001 R12: ffff8f5954978800
|
|
R13: ffff8f595287faf0 R14: ffff8f5953c77dd0 R15: 0000000000000065
|
|
FS: 00007fc5284c8c40(0000) GS:ffff8f59bbd00000(0000) knlGS:0000000000000000
|
|
CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
|
|
CR2: 00007fc5287f47c0 CR3: 000000011275e002 CR4: 0000000000370ee0
|
|
Call Trace:
|
|
replay_one_buffer+0x409/0x470
|
|
? btree_read_extent_buffer_pages+0xd0/0x110
|
|
walk_up_log_tree+0x157/0x1e0
|
|
walk_log_tree+0xa6/0x1d0
|
|
btrfs_recover_log_trees+0x1da/0x360
|
|
? replay_one_extent+0x7b0/0x7b0
|
|
open_ctree+0x1486/0x1720
|
|
btrfs_mount_root.cold+0x12/0xea
|
|
? __kmalloc_track_caller+0x12f/0x240
|
|
legacy_get_tree+0x24/0x40
|
|
vfs_get_tree+0x22/0xb0
|
|
vfs_kern_mount.part.0+0x71/0xb0
|
|
btrfs_mount+0x10d/0x380
|
|
? vfs_parse_fs_string+0x4d/0x90
|
|
legacy_get_tree+0x24/0x40
|
|
vfs_get_tree+0x22/0xb0
|
|
path_mount+0x433/0xa10
|
|
__x64_sys_mount+0xe3/0x120
|
|
do_syscall_64+0x3d/0x80
|
|
entry_SYSCALL_64_after_hwframe+0x44/0xae
|
|
|
|
We can get -EIO or any number of legitimate errors from
|
|
btrfs_search_slot(), panicing here is not the appropriate response. The
|
|
error path for this code handles errors properly, simply return the
|
|
error.(CVE-2021-47145)
|
|
|
|
In the Linux kernel, the following vulnerability has been resolved:
|
|
|
|
mld: fix panic in mld_newpack()
|
|
|
|
mld_newpack() doesn't allow to allocate high order page,
|
|
only order-0 allocation is allowed.
|
|
If headroom size is too large, a kernel panic could occur in skb_put().
|
|
|
|
Test commands:
|
|
ip netns del A
|
|
ip netns del B
|
|
ip netns add A
|
|
ip netns add B
|
|
ip link add veth0 type veth peer name veth1
|
|
ip link set veth0 netns A
|
|
ip link set veth1 netns B
|
|
|
|
ip netns exec A ip link set lo up
|
|
ip netns exec A ip link set veth0 up
|
|
ip netns exec A ip -6 a a 2001:db8:0::1/64 dev veth0
|
|
ip netns exec B ip link set lo up
|
|
ip netns exec B ip link set veth1 up
|
|
ip netns exec B ip -6 a a 2001:db8:0::2/64 dev veth1
|
|
for i in {1..99}
|
|
do
|
|
let A=$i-1
|
|
ip netns exec A ip link add ip6gre$i type ip6gre \
|
|
local 2001:db8:$A::1 remote 2001:db8:$A::2 encaplimit 100
|
|
ip netns exec A ip -6 a a 2001:db8:$i::1/64 dev ip6gre$i
|
|
ip netns exec A ip link set ip6gre$i up
|
|
|
|
ip netns exec B ip link add ip6gre$i type ip6gre \
|
|
local 2001:db8:$A::2 remote 2001:db8:$A::1 encaplimit 100
|
|
ip netns exec B ip -6 a a 2001:db8:$i::2/64 dev ip6gre$i
|
|
ip netns exec B ip link set ip6gre$i up
|
|
done
|
|
|
|
Splat looks like:
|
|
kernel BUG at net/core/skbuff.c:110!
|
|
invalid opcode: 0000 [#1] SMP DEBUG_PAGEALLOC KASAN PTI
|
|
CPU: 0 PID: 7 Comm: kworker/0:1 Not tainted 5.12.0+ #891
|
|
Workqueue: ipv6_addrconf addrconf_dad_work
|
|
RIP: 0010:skb_panic+0x15d/0x15f
|
|
Code: 92 fe 4c 8b 4c 24 10 53 8b 4d 70 45 89 e0 48 c7 c7 00 ae 79 83
|
|
41 57 41 56 41 55 48 8b 54 24 a6 26 f9 ff <0f> 0b 48 8b 6c 24 20 89
|
|
34 24 e8 4a 4e 92 fe 8b 34 24 48 c7 c1 20
|
|
RSP: 0018:ffff88810091f820 EFLAGS: 00010282
|
|
RAX: 0000000000000089 RBX: ffff8881086e9000 RCX: 0000000000000000
|
|
RDX: 0000000000000089 RSI: 0000000000000008 RDI: ffffed1020123efb
|
|
RBP: ffff888005f6eac0 R08: ffffed1022fc0031 R09: ffffed1022fc0031
|
|
R10: ffff888117e00187 R11: ffffed1022fc0030 R12: 0000000000000028
|
|
R13: ffff888008284eb0 R14: 0000000000000ed8 R15: 0000000000000ec0
|
|
FS: 0000000000000000(0000) GS:ffff888117c00000(0000)
|
|
knlGS:0000000000000000
|
|
CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
|
|
CR2: 00007f8b801c5640 CR3: 0000000033c2c006 CR4: 00000000003706f0
|
|
DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000
|
|
DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400
|
|
Call Trace:
|
|
? ip6_mc_hdr.isra.26.constprop.46+0x12a/0x600
|
|
? ip6_mc_hdr.isra.26.constprop.46+0x12a/0x600
|
|
skb_put.cold.104+0x22/0x22
|
|
ip6_mc_hdr.isra.26.constprop.46+0x12a/0x600
|
|
? rcu_read_lock_sched_held+0x91/0xc0
|
|
mld_newpack+0x398/0x8f0
|
|
? ip6_mc_hdr.isra.26.constprop.46+0x600/0x600
|
|
? lock_contended+0xc40/0xc40
|
|
add_grhead.isra.33+0x280/0x380
|
|
add_grec+0x5ca/0xff0
|
|
? mld_sendpack+0xf40/0xf40
|
|
? lock_downgrade+0x690/0x690
|
|
mld_send_initial_cr.part.34+0xb9/0x180
|
|
ipv6_mc_dad_complete+0x15d/0x1b0
|
|
addrconf_dad_completed+0x8d2/0xbb0
|
|
? lock_downgrade+0x690/0x690
|
|
? addrconf_rs_timer+0x660/0x660
|
|
? addrconf_dad_work+0x73c/0x10e0
|
|
addrconf_dad_work+0x73c/0x10e0
|
|
|
|
Allowing high order page allocation could fix this problem.(CVE-2021-47146)
|
|
|
|
In the Linux kernel, the following vulnerability has been resolved:
|
|
|
|
i2c: i801: Don't generate an interrupt on bus reset
|
|
|
|
Now that the i2c-i801 driver supports interrupts, setting the KILL bit
|
|
in a attempt to recover from a timed out transaction triggers an
|
|
interrupt. Unfortunately, the interrupt handler (i801_isr) is not
|
|
prepared for this situation and will try to process the interrupt as
|
|
if it was signaling the end of a successful transaction. In the case
|
|
of a block transaction, this can result in an out-of-range memory
|
|
access.
|
|
|
|
This condition was reproduced several times by syzbot:
|
|
https://syzkaller.appspot.com/bug?extid=ed71512d469895b5b34e
|
|
https://syzkaller.appspot.com/bug?extid=8c8dedc0ba9e03f6c79e
|
|
https://syzkaller.appspot.com/bug?extid=c8ff0b6d6c73d81b610e
|
|
https://syzkaller.appspot.com/bug?extid=33f6c360821c399d69eb
|
|
https://syzkaller.appspot.com/bug?extid=be15dc0b1933f04b043a
|
|
https://syzkaller.appspot.com/bug?extid=b4d3fd1dfd53e90afd79
|
|
|
|
So disable interrupts while trying to reset the bus. Interrupts will
|
|
be enabled again for the following transaction.(CVE-2021-47153)
|
|
|
|
In the Linux kernel, the following vulnerability has been resolved:
|
|
|
|
net: dsa: fix a crash if ->get_sset_count() fails
|
|
|
|
If ds->ops->get_sset_count() fails then it "count" is a negative error
|
|
code such as -EOPNOTSUPP. Because "i" is an unsigned int, the negative
|
|
error code is type promoted to a very high value and the loop will
|
|
corrupt memory until the system crashes.
|
|
|
|
Fix this by checking for error codes and changing the type of "i" to
|
|
just int.(CVE-2021-47159)
|
|
|
|
In the Linux kernel, the following vulnerability has been resolved:
|
|
|
|
net: dsa: mt7530: fix VLAN traffic leaks
|
|
|
|
PCR_MATRIX field was set to all 1's when VLAN filtering is enabled, but
|
|
was not reset when it is disabled, which may cause traffic leaks:
|
|
|
|
ip link add br0 type bridge vlan_filtering 1
|
|
ip link add br1 type bridge vlan_filtering 1
|
|
ip link set swp0 master br0
|
|
ip link set swp1 master br1
|
|
ip link set br0 type bridge vlan_filtering 0
|
|
ip link set br1 type bridge vlan_filtering 0
|
|
# traffic in br0 and br1 will start leaking to each other
|
|
|
|
As port_bridge_{add,del} have set up PCR_MATRIX properly, remove the
|
|
PCR_MATRIX write from mt7530_port_set_vlan_aware.(CVE-2021-47160)
|
|
|
|
In the Linux kernel, the following vulnerability has been resolved:
|
|
|
|
spi: spi-fsl-dspi: Fix a resource leak in an error handling path
|
|
|
|
'dspi_request_dma()' should be undone by a 'dspi_release_dma()' call in the
|
|
error handling path of the probe function, as already done in the remove
|
|
function(CVE-2021-47161)
|
|
|
|
In the Linux kernel, the following vulnerability has been resolved:
|
|
|
|
tipc: skb_linearize the head skb when reassembling msgs
|
|
|
|
It's not a good idea to append the frag skb to a skb's frag_list if
|
|
the frag_list already has skbs from elsewhere, such as this skb was
|
|
created by pskb_copy() where the frag_list was cloned (all the skbs
|
|
in it were skb_get'ed) and shared by multiple skbs.
|
|
|
|
However, the new appended frag skb should have been only seen by the
|
|
current skb. Otherwise, it will cause use after free crashes as this
|
|
appended frag skb are seen by multiple skbs but it only got skb_get
|
|
called once.
|
|
|
|
The same thing happens with a skb updated by pskb_may_pull() with a
|
|
skb_cloned skb. Li Shuang has reported quite a few crashes caused
|
|
by this when doing testing over macvlan devices:
|
|
|
|
[] kernel BUG at net/core/skbuff.c:1970!
|
|
[] Call Trace:
|
|
[] skb_clone+0x4d/0xb0
|
|
[] macvlan_broadcast+0xd8/0x160 [macvlan]
|
|
[] macvlan_process_broadcast+0x148/0x150 [macvlan]
|
|
[] process_one_work+0x1a7/0x360
|
|
[] worker_thread+0x30/0x390
|
|
|
|
[] kernel BUG at mm/usercopy.c:102!
|
|
[] Call Trace:
|
|
[] __check_heap_object+0xd3/0x100
|
|
[] __check_object_size+0xff/0x16b
|
|
[] simple_copy_to_iter+0x1c/0x30
|
|
[] __skb_datagram_iter+0x7d/0x310
|
|
[] __skb_datagram_iter+0x2a5/0x310
|
|
[] skb_copy_datagram_iter+0x3b/0x90
|
|
[] tipc_recvmsg+0x14a/0x3a0 [tipc]
|
|
[] ____sys_recvmsg+0x91/0x150
|
|
[] ___sys_recvmsg+0x7b/0xc0
|
|
|
|
[] kernel BUG at mm/slub.c:305!
|
|
[] Call Trace:
|
|
[] <IRQ>
|
|
[] kmem_cache_free+0x3ff/0x400
|
|
[] __netif_receive_skb_core+0x12c/0xc40
|
|
[] ? kmem_cache_alloc+0x12e/0x270
|
|
[] netif_receive_skb_internal+0x3d/0xb0
|
|
[] ? get_rx_page_info+0x8e/0xa0 [be2net]
|
|
[] be_poll+0x6ef/0xd00 [be2net]
|
|
[] ? irq_exit+0x4f/0x100
|
|
[] net_rx_action+0x149/0x3b0
|
|
|
|
...
|
|
|
|
This patch is to fix it by linearizing the head skb if it has frag_list
|
|
set in tipc_buf_append(). Note that we choose to do this before calling
|
|
skb_unshare(), as __skb_linearize() will avoid skb_copy(). Also, we can
|
|
not just drop the frag_list either as the early time.(CVE-2021-47162)
|
|
|
|
In the Linux kernel, the following vulnerability has been resolved:
|
|
|
|
tipc: wait and exit until all work queues are done
|
|
|
|
On some host, a crash could be triggered simply by repeating these
|
|
commands several times:
|
|
|
|
# modprobe tipc
|
|
# tipc bearer enable media udp name UDP1 localip 127.0.0.1
|
|
# rmmod tipc
|
|
|
|
[] BUG: unable to handle kernel paging request at ffffffffc096bb00
|
|
[] Workqueue: events 0xffffffffc096bb00
|
|
[] Call Trace:
|
|
[] ? process_one_work+0x1a7/0x360
|
|
[] ? worker_thread+0x30/0x390
|
|
[] ? create_worker+0x1a0/0x1a0
|
|
[] ? kthread+0x116/0x130
|
|
[] ? kthread_flush_work_fn+0x10/0x10
|
|
[] ? ret_from_fork+0x35/0x40
|
|
|
|
When removing the TIPC module, the UDP tunnel sock will be delayed to
|
|
release in a work queue as sock_release() can't be done in rtnl_lock().
|
|
If the work queue is schedule to run after the TIPC module is removed,
|
|
kernel will crash as the work queue function cleanup_beareri() code no
|
|
longer exists when trying to invoke it.
|
|
|
|
To fix it, this patch introduce a member wq_count in tipc_net to track
|
|
the numbers of work queues in schedule, and wait and exit until all
|
|
work queues are done in tipc_exit_net().(CVE-2021-47163)
|
|
|
|
In the Linux kernel, the following vulnerability has been resolved:
|
|
|
|
NFS: Fix an Oopsable condition in __nfs_pageio_add_request()
|
|
|
|
Ensure that nfs_pageio_error_cleanup() resets the mirror array contents,
|
|
so that the structure reflects the fact that it is now empty.
|
|
Also change the test in nfs_pageio_do_add_request() to be more robust by
|
|
checking whether or not the list is empty rather than relying on the
|
|
value of pg_count.(CVE-2021-47167)
|
|
|
|
In the Linux kernel, the following vulnerability has been resolved:
|
|
|
|
USB: usbfs: Don't WARN about excessively large memory allocations
|
|
|
|
Syzbot found that the kernel generates a WARNing if the user tries to
|
|
submit a bulk transfer through usbfs with a buffer that is way too
|
|
large. This isn't a bug in the kernel; it's merely an invalid request
|
|
from the user and the usbfs code does handle it correctly.
|
|
|
|
In theory the same thing can happen with async transfers, or with the
|
|
packet descriptor table for isochronous transfers.
|
|
|
|
To prevent the MM subsystem from complaining about these bad
|
|
allocation requests, add the __GFP_NOWARN flag to the kmalloc calls
|
|
for these buffers.(CVE-2021-47170)
|
|
|
|
In the Linux kernel, the following vulnerability has been resolved:
|
|
|
|
net: usb: fix memory leak in smsc75xx_bind
|
|
|
|
Syzbot reported memory leak in smsc75xx_bind().
|
|
The problem was is non-freed memory in case of
|
|
errors after memory allocation.
|
|
|
|
backtrace:
|
|
[<ffffffff84245b62>] kmalloc include/linux/slab.h:556 [inline]
|
|
[<ffffffff84245b62>] kzalloc include/linux/slab.h:686 [inline]
|
|
[<ffffffff84245b62>] smsc75xx_bind+0x7a/0x334 drivers/net/usb/smsc75xx.c:1460
|
|
[<ffffffff82b5b2e6>] usbnet_probe+0x3b6/0xc30 drivers/net/usb/usbnet.c:1728(CVE-2021-47171)
|
|
|
|
In the Linux kernel, the following vulnerability has been resolved:
|
|
|
|
misc/uss720: fix memory leak in uss720_probe
|
|
|
|
uss720_probe forgets to decrease the refcount of usbdev in uss720_probe.
|
|
Fix this by decreasing the refcount of usbdev by usb_put_dev.
|
|
|
|
BUG: memory leak
|
|
unreferenced object 0xffff888101113800 (size 2048):
|
|
comm "kworker/0:1", pid 7, jiffies 4294956777 (age 28.870s)
|
|
hex dump (first 32 bytes):
|
|
ff ff ff ff 31 00 00 00 00 00 00 00 00 00 00 00 ....1...........
|
|
00 00 00 00 00 00 00 00 00 00 00 00 03 00 00 00 ................
|
|
backtrace:
|
|
[<ffffffff82b8e822>] kmalloc include/linux/slab.h:554 [inline]
|
|
[<ffffffff82b8e822>] kzalloc include/linux/slab.h:684 [inline]
|
|
[<ffffffff82b8e822>] usb_alloc_dev+0x32/0x450 drivers/usb/core/usb.c:582
|
|
[<ffffffff82b98441>] hub_port_connect drivers/usb/core/hub.c:5129 [inline]
|
|
[<ffffffff82b98441>] hub_port_connect_change drivers/usb/core/hub.c:5363 [inline]
|
|
[<ffffffff82b98441>] port_event drivers/usb/core/hub.c:5509 [inline]
|
|
[<ffffffff82b98441>] hub_event+0x1171/0x20c0 drivers/usb/core/hub.c:5591
|
|
[<ffffffff81259229>] process_one_work+0x2c9/0x600 kernel/workqueue.c:2275
|
|
[<ffffffff81259b19>] worker_thread+0x59/0x5d0 kernel/workqueue.c:2421
|
|
[<ffffffff81261228>] kthread+0x178/0x1b0 kernel/kthread.c:292
|
|
[<ffffffff8100227f>] ret_from_fork+0x1f/0x30 arch/x86/entry/entry_64.S:294(CVE-2021-47173)
|
|
|
|
In the Linux kernel, the following vulnerability has been resolved:
|
|
|
|
NFC: nci: fix memory leak in nci_allocate_device
|
|
|
|
nfcmrvl_disconnect fails to free the hci_dev field in struct nci_dev.
|
|
Fix this by freeing hci_dev in nci_free_device.
|
|
|
|
BUG: memory leak
|
|
unreferenced object 0xffff888111ea6800 (size 1024):
|
|
comm "kworker/1:0", pid 19, jiffies 4294942308 (age 13.580s)
|
|
hex dump (first 32 bytes):
|
|
00 00 00 00 00 00 00 00 00 60 fd 0c 81 88 ff ff .........`......
|
|
00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................
|
|
backtrace:
|
|
[<000000004bc25d43>] kmalloc include/linux/slab.h:552 [inline]
|
|
[<000000004bc25d43>] kzalloc include/linux/slab.h:682 [inline]
|
|
[<000000004bc25d43>] nci_hci_allocate+0x21/0xd0 net/nfc/nci/hci.c:784
|
|
[<00000000c59cff92>] nci_allocate_device net/nfc/nci/core.c:1170 [inline]
|
|
[<00000000c59cff92>] nci_allocate_device+0x10b/0x160 net/nfc/nci/core.c:1132
|
|
[<00000000006e0a8e>] nfcmrvl_nci_register_dev+0x10a/0x1c0 drivers/nfc/nfcmrvl/main.c:153
|
|
[<000000004da1b57e>] nfcmrvl_probe+0x223/0x290 drivers/nfc/nfcmrvl/usb.c:345
|
|
[<00000000d506aed9>] usb_probe_interface+0x177/0x370 drivers/usb/core/driver.c:396
|
|
[<00000000bc632c92>] really_probe+0x159/0x4a0 drivers/base/dd.c:554
|
|
[<00000000f5009125>] driver_probe_device+0x84/0x100 drivers/base/dd.c:740
|
|
[<000000000ce658ca>] __device_attach_driver+0xee/0x110 drivers/base/dd.c:846
|
|
[<000000007067d05f>] bus_for_each_drv+0xb7/0x100 drivers/base/bus.c:431
|
|
[<00000000f8e13372>] __device_attach+0x122/0x250 drivers/base/dd.c:914
|
|
[<000000009cf68860>] bus_probe_device+0xc6/0xe0 drivers/base/bus.c:491
|
|
[<00000000359c965a>] device_add+0x5be/0xc30 drivers/base/core.c:3109
|
|
[<00000000086e4bd3>] usb_set_configuration+0x9d9/0xb90 drivers/usb/core/message.c:2164
|
|
[<00000000ca036872>] usb_generic_driver_probe+0x8c/0xc0 drivers/usb/core/generic.c:238
|
|
[<00000000d40d36f6>] usb_probe_device+0x5c/0x140 drivers/usb/core/driver.c:293
|
|
[<00000000bc632c92>] really_probe+0x159/0x4a0 drivers/base/dd.c:554(CVE-2021-47180)
|
|
|
|
In the Linux kernel, the following vulnerability has been resolved:
|
|
|
|
EDAC/thunderx: Fix possible out-of-bounds string access
|
|
|
|
Enabling -Wstringop-overflow globally exposes a warning for a common bug
|
|
in the usage of strncat():
|
|
|
|
drivers/edac/thunderx_edac.c: In function 'thunderx_ocx_com_threaded_isr':
|
|
drivers/edac/thunderx_edac.c:1136:17: error: 'strncat' specified bound 1024 equals destination size [-Werror=stringop-overflow=]
|
|
1136 | strncat(msg, other, OCX_MESSAGE_SIZE);
|
|
| ^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
|
|
...
|
|
1145 | strncat(msg, other, OCX_MESSAGE_SIZE);
|
|
...
|
|
1150 | strncat(msg, other, OCX_MESSAGE_SIZE);
|
|
|
|
...
|
|
|
|
Apparently the author of this driver expected strncat() to behave the
|
|
way that strlcat() does, which uses the size of the destination buffer
|
|
as its third argument rather than the length of the source buffer. The
|
|
result is that there is no check on the size of the allocated buffer.
|
|
|
|
Change it to strlcat().
|
|
|
|
[ bp: Trim compiler output, fixup commit message. ](CVE-2023-52464)
|
|
|
|
In the Linux kernel, the following vulnerability has been resolved:
|
|
|
|
Input: powermate - fix use-after-free in powermate_config_complete
|
|
|
|
syzbot has found a use-after-free bug [1] in the powermate driver. This
|
|
happens when the device is disconnected, which leads to a memory free from
|
|
the powermate_device struct. When an asynchronous control message
|
|
completes after the kfree and its callback is invoked, the lock does not
|
|
exist anymore and hence the bug.
|
|
|
|
Use usb_kill_urb() on pm->config to cancel any in-progress requests upon
|
|
device disconnection.
|
|
|
|
[1] https://syzkaller.appspot.com/bug?extid=0434ac83f907a1dbdd1e(CVE-2023-52475)
|
|
|
|
In the Linux kernel, the following vulnerability has been resolved:
|
|
|
|
scsi: pm80xx: Avoid leaking tags when processing OPC_INB_SET_CONTROLLER_CONFIG command
|
|
|
|
Tags allocated for OPC_INB_SET_CONTROLLER_CONFIG command need to be freed
|
|
when we receive the response.(CVE-2023-52500)
|
|
|
|
In the Linux kernel, the following vulnerability has been resolved:
|
|
|
|
nfc: nci: assert requested protocol is valid
|
|
|
|
The protocol is used in a bit mask to determine if the protocol is
|
|
supported. Assert the provided protocol is less than the maximum
|
|
defined so it doesn't potentially perform a shift-out-of-bounds and
|
|
provide a clearer error for undefined protocols vs unsupported ones.(CVE-2023-52507)
|
|
|
|
In the Linux kernel, the following vulnerability has been resolved:
|
|
|
|
ieee802154: ca8210: Fix a potential UAF in ca8210_probe
|
|
|
|
If of_clk_add_provider() fails in ca8210_register_ext_clock(),
|
|
it calls clk_unregister() to release priv->clk and returns an
|
|
error. However, the caller ca8210_probe() then calls ca8210_remove(),
|
|
where priv->clk is freed again in ca8210_unregister_ext_clock(). In
|
|
this case, a use-after-free may happen in the second time we call
|
|
clk_unregister().
|
|
|
|
Fix this by removing the first clk_unregister(). Also, priv->clk could
|
|
be an error code on failure of clk_register_fixed_rate(). Use
|
|
IS_ERR_OR_NULL to catch this case in ca8210_unregister_ext_clock().(CVE-2023-52510)
|
|
|
|
In the Linux kernel, the following vulnerability has been resolved:
|
|
|
|
RDMA/srp: Do not call scsi_done() from srp_abort()
|
|
|
|
After scmd_eh_abort_handler() has called the SCSI LLD eh_abort_handler
|
|
callback, it performs one of the following actions:
|
|
* Call scsi_queue_insert().
|
|
* Call scsi_finish_command().
|
|
* Call scsi_eh_scmd_add().
|
|
Hence, SCSI abort handlers must not call scsi_done(). Otherwise all
|
|
the above actions would trigger a use-after-free. Hence remove the
|
|
scsi_done() call from srp_abort(). Keep the srp_free_req() call
|
|
before returning SUCCESS because we may not see the command again if
|
|
SUCCESS is returned.(CVE-2023-52515)
|
|
|
|
In the Linux kernel, the following vulnerability has been resolved:
|
|
|
|
net: fix possible store tearing in neigh_periodic_work()
|
|
|
|
While looking at a related syzbot report involving neigh_periodic_work(),
|
|
I found that I forgot to add an annotation when deleting an
|
|
RCU protected item from a list.
|
|
|
|
Readers use rcu_deference(*np), we need to use either
|
|
rcu_assign_pointer() or WRITE_ONCE() on writer side
|
|
to prevent store tearing.
|
|
|
|
I use rcu_assign_pointer() to have lockdep support,
|
|
this was the choice made in neigh_flush_dev().(CVE-2023-52522)
|
|
|
|
In the Linux kernel, the following vulnerability has been resolved:
|
|
|
|
wifi: mac80211: fix potential key use-after-free
|
|
|
|
When ieee80211_key_link() is called by ieee80211_gtk_rekey_add()
|
|
but returns 0 due to KRACK protection (identical key reinstall),
|
|
ieee80211_gtk_rekey_add() will still return a pointer into the
|
|
key, in a potential use-after-free. This normally doesn't happen
|
|
since it's only called by iwlwifi in case of WoWLAN rekey offload
|
|
which has its own KRACK protection, but still better to fix, do
|
|
that by returning an error code and converting that to success on
|
|
the cfg80211 boundary only, leaving the error for bad callers of
|
|
ieee80211_gtk_rekey_add().(CVE-2023-52530)
|
|
|
|
In the Linux kernel, the following vulnerability has been resolved:
|
|
|
|
nilfs2: fix potential use after free in nilfs_gccache_submit_read_data()
|
|
|
|
In nilfs_gccache_submit_read_data(), brelse(bh) is called to drop the
|
|
reference count of bh when the call to nilfs_dat_translate() fails. If
|
|
the reference count hits 0 and its owner page gets unlocked, bh may be
|
|
freed. However, bh->b_page is dereferenced to put the page after that,
|
|
which may result in a use-after-free bug. This patch moves the release
|
|
operation after unlocking and putting the page.
|
|
|
|
NOTE: The function in question is only called in GC, and in combination
|
|
with current userland tools, address translation using DAT does not occur
|
|
in that function, so the code path that causes this issue will not be
|
|
executed. However, it is possible to run that code path by intentionally
|
|
modifying the userland GC library or by calling the GC ioctl directly.
|
|
|
|
[konishi.ryusuke@gmail.com: NOTE added to the commit log](CVE-2023-52566)
|
|
|
|
In the Linux kernel, the following vulnerability has been resolved:
|
|
|
|
net: bridge: use DEV_STATS_INC()
|
|
|
|
syzbot/KCSAN reported data-races in br_handle_frame_finish() [1]
|
|
This function can run from multiple cpus without mutual exclusion.
|
|
|
|
Adopt SMP safe DEV_STATS_INC() to update dev->stats fields.
|
|
|
|
Handles updates to dev->stats.tx_dropped while we are at it.
|
|
|
|
[1]
|
|
BUG: KCSAN: data-race in br_handle_frame_finish / br_handle_frame_finish
|
|
|
|
read-write to 0xffff8881374b2178 of 8 bytes by interrupt on cpu 1:
|
|
br_handle_frame_finish+0xd4f/0xef0 net/bridge/br_input.c:189
|
|
br_nf_hook_thresh+0x1ed/0x220
|
|
br_nf_pre_routing_finish_ipv6+0x50f/0x540
|
|
NF_HOOK include/linux/netfilter.h:304 [inline]
|
|
br_nf_pre_routing_ipv6+0x1e3/0x2a0 net/bridge/br_netfilter_ipv6.c:178
|
|
br_nf_pre_routing+0x526/0xba0 net/bridge/br_netfilter_hooks.c:508
|
|
nf_hook_entry_hookfn include/linux/netfilter.h:144 [inline]
|
|
nf_hook_bridge_pre net/bridge/br_input.c:272 [inline]
|
|
br_handle_frame+0x4c9/0x940 net/bridge/br_input.c:417
|
|
__netif_receive_skb_core+0xa8a/0x21e0 net/core/dev.c:5417
|
|
__netif_receive_skb_one_core net/core/dev.c:5521 [inline]
|
|
__netif_receive_skb+0x57/0x1b0 net/core/dev.c:5637
|
|
process_backlog+0x21f/0x380 net/core/dev.c:5965
|
|
__napi_poll+0x60/0x3b0 net/core/dev.c:6527
|
|
napi_poll net/core/dev.c:6594 [inline]
|
|
net_rx_action+0x32b/0x750 net/core/dev.c:6727
|
|
__do_softirq+0xc1/0x265 kernel/softirq.c:553
|
|
run_ksoftirqd+0x17/0x20 kernel/softirq.c:921
|
|
smpboot_thread_fn+0x30a/0x4a0 kernel/smpboot.c:164
|
|
kthread+0x1d7/0x210 kernel/kthread.c:388
|
|
ret_from_fork+0x48/0x60 arch/x86/kernel/process.c:147
|
|
ret_from_fork_asm+0x11/0x20 arch/x86/entry/entry_64.S:304
|
|
|
|
read-write to 0xffff8881374b2178 of 8 bytes by interrupt on cpu 0:
|
|
br_handle_frame_finish+0xd4f/0xef0 net/bridge/br_input.c:189
|
|
br_nf_hook_thresh+0x1ed/0x220
|
|
br_nf_pre_routing_finish_ipv6+0x50f/0x540
|
|
NF_HOOK include/linux/netfilter.h:304 [inline]
|
|
br_nf_pre_routing_ipv6+0x1e3/0x2a0 net/bridge/br_netfilter_ipv6.c:178
|
|
br_nf_pre_routing+0x526/0xba0 net/bridge/br_netfilter_hooks.c:508
|
|
nf_hook_entry_hookfn include/linux/netfilter.h:144 [inline]
|
|
nf_hook_bridge_pre net/bridge/br_input.c:272 [inline]
|
|
br_handle_frame+0x4c9/0x940 net/bridge/br_input.c:417
|
|
__netif_receive_skb_core+0xa8a/0x21e0 net/core/dev.c:5417
|
|
__netif_receive_skb_one_core net/core/dev.c:5521 [inline]
|
|
__netif_receive_skb+0x57/0x1b0 net/core/dev.c:5637
|
|
process_backlog+0x21f/0x380 net/core/dev.c:5965
|
|
__napi_poll+0x60/0x3b0 net/core/dev.c:6527
|
|
napi_poll net/core/dev.c:6594 [inline]
|
|
net_rx_action+0x32b/0x750 net/core/dev.c:6727
|
|
__do_softirq+0xc1/0x265 kernel/softirq.c:553
|
|
do_softirq+0x5e/0x90 kernel/softirq.c:454
|
|
__local_bh_enable_ip+0x64/0x70 kernel/softirq.c:381
|
|
__raw_spin_unlock_bh include/linux/spinlock_api_smp.h:167 [inline]
|
|
_raw_spin_unlock_bh+0x36/0x40 kernel/locking/spinlock.c:210
|
|
spin_unlock_bh include/linux/spinlock.h:396 [inline]
|
|
batadv_tt_local_purge+0x1a8/0x1f0 net/batman-adv/translation-table.c:1356
|
|
batadv_tt_purge+0x2b/0x630 net/batman-adv/translation-table.c:3560
|
|
process_one_work kernel/workqueue.c:2630 [inline]
|
|
process_scheduled_works+0x5b8/0xa30 kernel/workqueue.c:2703
|
|
worker_thread+0x525/0x730 kernel/workqueue.c:2784
|
|
kthread+0x1d7/0x210 kernel/kthread.c:388
|
|
ret_from_fork+0x48/0x60 arch/x86/kernel/process.c:147
|
|
ret_from_fork_asm+0x11/0x20 arch/x86/entry/entry_64.S:304
|
|
|
|
value changed: 0x00000000000d7190 -> 0x00000000000d7191
|
|
|
|
Reported by Kernel Concurrency Sanitizer on:
|
|
CPU: 0 PID: 14848 Comm: kworker/u4:11 Not tainted 6.6.0-rc1-syzkaller-00236-gad8a69f361b9 #0(CVE-2023-52578)
|
|
|
|
In the Linux kernel, the following vulnerability has been resolved:
|
|
|
|
ceph: fix deadlock or deadcode of misusing dget()
|
|
|
|
The lock order is incorrect between denty and its parent, we should
|
|
always make sure that the parent get the lock first.
|
|
|
|
But since this deadcode is never used and the parent dir will always
|
|
be set from the callers, let's just remove it.(CVE-2023-52583)
|
|
|
|
In the Linux kernel, the following vulnerability has been resolved:
|
|
|
|
IB/ipoib: Fix mcast list locking
|
|
|
|
Releasing the `priv->lock` while iterating the `priv->multicast_list` in
|
|
`ipoib_mcast_join_task()` opens a window for `ipoib_mcast_dev_flush()` to
|
|
remove the items while in the middle of iteration. If the mcast is removed
|
|
while the lock was dropped, the for loop spins forever resulting in a hard
|
|
lockup (as was reported on RHEL 4.18.0-372.75.1.el8_6 kernel):
|
|
|
|
Task A (kworker/u72:2 below) | Task B (kworker/u72:0 below)
|
|
-----------------------------------+-----------------------------------
|
|
ipoib_mcast_join_task(work) | ipoib_ib_dev_flush_light(work)
|
|
spin_lock_irq(&priv->lock) | __ipoib_ib_dev_flush(priv, ...)
|
|
list_for_each_entry(mcast, | ipoib_mcast_dev_flush(dev = priv->dev)
|
|
&priv->multicast_list, list) |
|
|
ipoib_mcast_join(dev, mcast) |
|
|
spin_unlock_irq(&priv->lock) |
|
|
| spin_lock_irqsave(&priv->lock, flags)
|
|
| list_for_each_entry_safe(mcast, tmcast,
|
|
| &priv->multicast_list, list)
|
|
| list_del(&mcast->list);
|
|
| list_add_tail(&mcast->list, &remove_list)
|
|
| spin_unlock_irqrestore(&priv->lock, flags)
|
|
spin_lock_irq(&priv->lock) |
|
|
| ipoib_mcast_remove_list(&remove_list)
|
|
(Here, `mcast` is no longer on the | list_for_each_entry_safe(mcast, tmcast,
|
|
`priv->multicast_list` and we keep | remove_list, list)
|
|
spinning on the `remove_list` of | >>> wait_for_completion(&mcast->done)
|
|
the other thread which is blocked |
|
|
and the list is still valid on |
|
|
it's stack.)
|
|
|
|
Fix this by keeping the lock held and changing to GFP_ATOMIC to prevent
|
|
eventual sleeps.
|
|
Unfortunately we could not reproduce the lockup and confirm this fix but
|
|
based on the code review I think this fix should address such lockups.
|
|
|
|
crash> bc 31
|
|
PID: 747 TASK: ff1c6a1a007e8000 CPU: 31 COMMAND: "kworker/u72:2"
|
|
--
|
|
[exception RIP: ipoib_mcast_join_task+0x1b1]
|
|
RIP: ffffffffc0944ac1 RSP: ff646f199a8c7e00 RFLAGS: 00000002
|
|
RAX: 0000000000000000 RBX: ff1c6a1a04dc82f8 RCX: 0000000000000000
|
|
work (&priv->mcast_task{,.work})
|
|
RDX: ff1c6a192d60ac68 RSI: 0000000000000286 RDI: ff1c6a1a04dc8000
|
|
&mcast->list
|
|
RBP: ff646f199a8c7e90 R8: ff1c699980019420 R9: ff1c6a1920c9a000
|
|
R10: ff646f199a8c7e00 R11: ff1c6a191a7d9800 R12: ff1c6a192d60ac00
|
|
mcast
|
|
R13: ff1c6a1d82200000 R14: ff1c6a1a04dc8000 R15: ff1c6a1a04dc82d8
|
|
dev priv (&priv->lock) &priv->multicast_list (aka head)
|
|
ORIG_RAX: ffffffffffffffff CS: 0010 SS: 0018
|
|
--- <NMI exception stack> ---
|
|
#5 [ff646f199a8c7e00] ipoib_mcast_join_task+0x1b1 at ffffffffc0944ac1 [ib_ipoib]
|
|
#6 [ff646f199a8c7e98] process_one_work+0x1a7 at ffffffff9bf10967
|
|
|
|
crash> rx ff646f199a8c7e68
|
|
ff646f199a8c7e68: ff1c6a1a04dc82f8 <<< work = &priv->mcast_task.work
|
|
|
|
crash> list -hO ipoib_dev_priv.multicast_list ff1c6a1a04dc8000
|
|
(empty)
|
|
|
|
crash> ipoib_dev_priv.mcast_task.work.func,mcast_mutex.owner.counter ff1c6a1a04dc8000
|
|
mcast_task.work.func = 0xffffffffc0944910 <ipoib_mcast_join_task>,
|
|
mcast_mutex.owner.counter = 0xff1c69998efec000
|
|
|
|
crash> b 8
|
|
PID: 8 TASK: ff1c69998efec000 CPU: 33 COMMAND: "kworker/u72:0"
|
|
--
|
|
#3 [ff646f1980153d50] wait_for_completion+0x96 at ffffffff9c7d7646
|
|
#4 [ff646f1980153d90] ipoib_mcast_remove_list+0x56 at ffffffffc0944dc6 [ib_ipoib]
|
|
#5 [ff646f1980153de8] ipoib_mcast_dev_flush+0x1a7 at ffffffffc09455a7 [ib_ipoib]
|
|
#6 [ff646f1980153e58] __ipoib_ib_dev_flush+0x1a4 at ffffffffc09431a4 [ib_ipoib]
|
|
#7 [ff
|
|
---truncated---(CVE-2023-52587)
|
|
|
|
In the Linux kernel, the following vulnerability has been resolved:
|
|
|
|
wifi: ath9k: Fix potential array-index-out-of-bounds read in ath9k_htc_txstatus()
|
|
|
|
Fix an array-index-out-of-bounds read in ath9k_htc_txstatus(). The bug
|
|
occurs when txs->cnt, data from a URB provided by a USB device, is
|
|
bigger than the size of the array txs->txstatus, which is
|
|
HTC_MAX_TX_STATUS. WARN_ON() already checks it, but there is no bug
|
|
handling code after the check. Make the function return if that is the
|
|
case.
|
|
|
|
Found by a modified version of syzkaller.
|
|
|
|
UBSAN: array-index-out-of-bounds in htc_drv_txrx.c
|
|
index 13 is out of range for type '__wmi_event_txstatus [12]'
|
|
Call Trace:
|
|
ath9k_htc_txstatus
|
|
ath9k_wmi_event_tasklet
|
|
tasklet_action_common
|
|
__do_softirq
|
|
irq_exit_rxu
|
|
sysvec_apic_timer_interrupt(CVE-2023-52594)
|
|
|
|
In the Linux kernel, the following vulnerability has been resolved:
|
|
|
|
wifi: rt2x00: restart beacon queue when hardware reset
|
|
|
|
When a hardware reset is triggered, all registers are reset, so all
|
|
queues are forced to stop in hardware interface. However, mac80211
|
|
will not automatically stop the queue. If we don't manually stop the
|
|
beacon queue, the queue will be deadlocked and unable to start again.
|
|
This patch fixes the issue where Apple devices cannot connect to the
|
|
AP after calling ieee80211_restart_hw().(CVE-2023-52595)
|
|
|
|
In the Linux kernel, the following vulnerability has been resolved:
|
|
|
|
KVM: s390: fix setting of fpc register
|
|
|
|
kvm_arch_vcpu_ioctl_set_fpu() allows to set the floating point control
|
|
(fpc) register of a guest cpu. The new value is tested for validity by
|
|
temporarily loading it into the fpc register.
|
|
|
|
This may lead to corruption of the fpc register of the host process:
|
|
if an interrupt happens while the value is temporarily loaded into the fpc
|
|
register, and within interrupt context floating point or vector registers
|
|
are used, the current fp/vx registers are saved with save_fpu_regs()
|
|
assuming they belong to user space and will be loaded into fp/vx registers
|
|
when returning to user space.
|
|
|
|
test_fp_ctl() restores the original user space / host process fpc register
|
|
value, however it will be discarded, when returning to user space.
|
|
|
|
In result the host process will incorrectly continue to run with the value
|
|
that was supposed to be used for a guest cpu.
|
|
|
|
Fix this by simply removing the test. There is another test right before
|
|
the SIE context is entered which will handles invalid values.
|
|
|
|
This results in a change of behaviour: invalid values will now be accepted
|
|
instead of that the ioctl fails with -EINVAL. This seems to be acceptable,
|
|
given that this interface is most likely not used anymore, and this is in
|
|
addition the same behaviour implemented with the memory mapped interface
|
|
(replace invalid values with zero) - see sync_regs() in kvm-s390.c.(CVE-2023-52597)
|
|
|
|
In the Linux kernel, the following vulnerability has been resolved:
|
|
|
|
s390/ptrace: handle setting of fpc register correctly
|
|
|
|
If the content of the floating point control (fpc) register of a traced
|
|
process is modified with the ptrace interface the new value is tested for
|
|
validity by temporarily loading it into the fpc register.
|
|
|
|
This may lead to corruption of the fpc register of the tracing process:
|
|
if an interrupt happens while the value is temporarily loaded into the
|
|
fpc register, and within interrupt context floating point or vector
|
|
registers are used, the current fp/vx registers are saved with
|
|
save_fpu_regs() assuming they belong to user space and will be loaded into
|
|
fp/vx registers when returning to user space.
|
|
|
|
test_fp_ctl() restores the original user space fpc register value, however
|
|
it will be discarded, when returning to user space.
|
|
|
|
In result the tracer will incorrectly continue to run with the value that
|
|
was supposed to be used for the traced process.
|
|
|
|
Fix this by saving fpu register contents with save_fpu_regs() before using
|
|
test_fp_ctl().(CVE-2023-52598)
|
|
|
|
In the Linux kernel, the following vulnerability has been resolved:
|
|
|
|
ext4: avoid online resizing failures due to oversized flex bg
|
|
|
|
When we online resize an ext4 filesystem with a oversized flexbg_size,
|
|
|
|
mkfs.ext4 -F -G 67108864 $dev -b 4096 100M
|
|
mount $dev $dir
|
|
resize2fs $dev 16G
|
|
|
|
the following WARN_ON is triggered:
|
|
==================================================================
|
|
WARNING: CPU: 0 PID: 427 at mm/page_alloc.c:4402 __alloc_pages+0x411/0x550
|
|
Modules linked in: sg(E)
|
|
CPU: 0 PID: 427 Comm: resize2fs Tainted: G E 6.6.0-rc5+ #314
|
|
RIP: 0010:__alloc_pages+0x411/0x550
|
|
Call Trace:
|
|
<TASK>
|
|
__kmalloc_large_node+0xa2/0x200
|
|
__kmalloc+0x16e/0x290
|
|
ext4_resize_fs+0x481/0xd80
|
|
__ext4_ioctl+0x1616/0x1d90
|
|
ext4_ioctl+0x12/0x20
|
|
__x64_sys_ioctl+0xf0/0x150
|
|
do_syscall_64+0x3b/0x90
|
|
==================================================================
|
|
|
|
This is because flexbg_size is too large and the size of the new_group_data
|
|
array to be allocated exceeds MAX_ORDER. Currently, the minimum value of
|
|
MAX_ORDER is 8, the minimum value of PAGE_SIZE is 4096, the corresponding
|
|
maximum number of groups that can be allocated is:
|
|
|
|
(PAGE_SIZE << MAX_ORDER) / sizeof(struct ext4_new_group_data) ≈ 21845
|
|
|
|
And the value that is down-aligned to the power of 2 is 16384. Therefore,
|
|
this value is defined as MAX_RESIZE_BG, and the number of groups added
|
|
each time does not exceed this value during resizing, and is added multiple
|
|
times to complete the online resizing. The difference is that the metadata
|
|
in a flex_bg may be more dispersed.(CVE-2023-52622)</Note>
|
|
<Note Title="Topic" Type="General" Ordinal="4" xml:lang="en">An update for kernel is now available for openEuler-20.03-LTS-SP4.
|
|
|
|
openEuler Security has rated this update as having a security impact of high. A Common Vunlnerability Scoring System(CVSS)base score,which gives a detailed severity rating, is available for each vulnerability from the CVElink(s) in the References section.</Note>
|
|
<Note Title="Severity" Type="General" Ordinal="5" xml:lang="en">High</Note>
|
|
<Note Title="Affected Component" Type="General" Ordinal="6" xml:lang="en">kernel</Note>
|
|
</DocumentNotes>
|
|
<DocumentReferences>
|
|
<Reference Type="Self">
|
|
<URL>https://www.openeuler.org/en/security/safety-bulletin/detail.html?id=openEuler-SA-2024-1484</URL>
|
|
</Reference>
|
|
<Reference Type="openEuler CVE">
|
|
<URL>https://www.openeuler.org/en/security/cve/detail.html?id=CVE-2020-36783</URL>
|
|
<URL>https://www.openeuler.org/en/security/cve/detail.html?id=CVE-2021-46984</URL>
|
|
<URL>https://www.openeuler.org/en/security/cve/detail.html?id=CVE-2021-47054</URL>
|
|
<URL>https://www.openeuler.org/en/security/cve/detail.html?id=CVE-2021-47056</URL>
|
|
<URL>https://www.openeuler.org/en/security/cve/detail.html?id=CVE-2021-47060</URL>
|
|
<URL>https://www.openeuler.org/en/security/cve/detail.html?id=CVE-2021-47061</URL>
|
|
<URL>https://www.openeuler.org/en/security/cve/detail.html?id=CVE-2021-47063</URL>
|
|
<URL>https://www.openeuler.org/en/security/cve/detail.html?id=CVE-2021-47071</URL>
|
|
<URL>https://www.openeuler.org/en/security/cve/detail.html?id=CVE-2021-47074</URL>
|
|
<URL>https://www.openeuler.org/en/security/cve/detail.html?id=CVE-2021-47077</URL>
|
|
<URL>https://www.openeuler.org/en/security/cve/detail.html?id=CVE-2021-47078</URL>
|
|
<URL>https://www.openeuler.org/en/security/cve/detail.html?id=CVE-2021-47101</URL>
|
|
<URL>https://www.openeuler.org/en/security/cve/detail.html?id=CVE-2021-47131</URL>
|
|
<URL>https://www.openeuler.org/en/security/cve/detail.html?id=CVE-2021-47142</URL>
|
|
<URL>https://www.openeuler.org/en/security/cve/detail.html?id=CVE-2021-47143</URL>
|
|
<URL>https://www.openeuler.org/en/security/cve/detail.html?id=CVE-2021-47144</URL>
|
|
<URL>https://www.openeuler.org/en/security/cve/detail.html?id=CVE-2021-47145</URL>
|
|
<URL>https://www.openeuler.org/en/security/cve/detail.html?id=CVE-2021-47146</URL>
|
|
<URL>https://www.openeuler.org/en/security/cve/detail.html?id=CVE-2021-47153</URL>
|
|
<URL>https://www.openeuler.org/en/security/cve/detail.html?id=CVE-2021-47159</URL>
|
|
<URL>https://www.openeuler.org/en/security/cve/detail.html?id=CVE-2021-47160</URL>
|
|
<URL>https://www.openeuler.org/en/security/cve/detail.html?id=CVE-2021-47161</URL>
|
|
<URL>https://www.openeuler.org/en/security/cve/detail.html?id=CVE-2021-47162</URL>
|
|
<URL>https://www.openeuler.org/en/security/cve/detail.html?id=CVE-2021-47163</URL>
|
|
<URL>https://www.openeuler.org/en/security/cve/detail.html?id=CVE-2021-47167</URL>
|
|
<URL>https://www.openeuler.org/en/security/cve/detail.html?id=CVE-2021-47170</URL>
|
|
<URL>https://www.openeuler.org/en/security/cve/detail.html?id=CVE-2021-47171</URL>
|
|
<URL>https://www.openeuler.org/en/security/cve/detail.html?id=CVE-2021-47173</URL>
|
|
<URL>https://www.openeuler.org/en/security/cve/detail.html?id=CVE-2021-47180</URL>
|
|
<URL>https://www.openeuler.org/en/security/cve/detail.html?id=CVE-2023-52464</URL>
|
|
<URL>https://www.openeuler.org/en/security/cve/detail.html?id=CVE-2023-52475</URL>
|
|
<URL>https://www.openeuler.org/en/security/cve/detail.html?id=CVE-2023-52500</URL>
|
|
<URL>https://www.openeuler.org/en/security/cve/detail.html?id=CVE-2023-52507</URL>
|
|
<URL>https://www.openeuler.org/en/security/cve/detail.html?id=CVE-2023-52510</URL>
|
|
<URL>https://www.openeuler.org/en/security/cve/detail.html?id=CVE-2023-52515</URL>
|
|
<URL>https://www.openeuler.org/en/security/cve/detail.html?id=CVE-2023-52522</URL>
|
|
<URL>https://www.openeuler.org/en/security/cve/detail.html?id=CVE-2023-52530</URL>
|
|
<URL>https://www.openeuler.org/en/security/cve/detail.html?id=CVE-2023-52566</URL>
|
|
<URL>https://www.openeuler.org/en/security/cve/detail.html?id=CVE-2023-52578</URL>
|
|
<URL>https://www.openeuler.org/en/security/cve/detail.html?id=CVE-2023-52583</URL>
|
|
<URL>https://www.openeuler.org/en/security/cve/detail.html?id=CVE-2023-52587</URL>
|
|
<URL>https://www.openeuler.org/en/security/cve/detail.html?id=CVE-2023-52594</URL>
|
|
<URL>https://www.openeuler.org/en/security/cve/detail.html?id=CVE-2023-52595</URL>
|
|
<URL>https://www.openeuler.org/en/security/cve/detail.html?id=CVE-2023-52597</URL>
|
|
<URL>https://www.openeuler.org/en/security/cve/detail.html?id=CVE-2023-52598</URL>
|
|
<URL>https://www.openeuler.org/en/security/cve/detail.html?id=CVE-2023-52622</URL>
|
|
</Reference>
|
|
<Reference Type="Other">
|
|
<URL>https://nvd.nist.gov/vuln/detail/CVE-2020-36783</URL>
|
|
<URL>https://nvd.nist.gov/vuln/detail/CVE-2021-46984</URL>
|
|
<URL>https://nvd.nist.gov/vuln/detail/CVE-2021-47054</URL>
|
|
<URL>https://nvd.nist.gov/vuln/detail/CVE-2021-47056</URL>
|
|
<URL>https://nvd.nist.gov/vuln/detail/CVE-2021-47060</URL>
|
|
<URL>https://nvd.nist.gov/vuln/detail/CVE-2021-47061</URL>
|
|
<URL>https://nvd.nist.gov/vuln/detail/CVE-2021-47063</URL>
|
|
<URL>https://nvd.nist.gov/vuln/detail/CVE-2021-47071</URL>
|
|
<URL>https://nvd.nist.gov/vuln/detail/CVE-2021-47074</URL>
|
|
<URL>https://nvd.nist.gov/vuln/detail/CVE-2021-47077</URL>
|
|
<URL>https://nvd.nist.gov/vuln/detail/CVE-2021-47078</URL>
|
|
<URL>https://nvd.nist.gov/vuln/detail/CVE-2021-47101</URL>
|
|
<URL>https://nvd.nist.gov/vuln/detail/CVE-2021-47131</URL>
|
|
<URL>https://nvd.nist.gov/vuln/detail/CVE-2021-47142</URL>
|
|
<URL>https://nvd.nist.gov/vuln/detail/CVE-2021-47143</URL>
|
|
<URL>https://nvd.nist.gov/vuln/detail/CVE-2021-47144</URL>
|
|
<URL>https://nvd.nist.gov/vuln/detail/CVE-2021-47145</URL>
|
|
<URL>https://nvd.nist.gov/vuln/detail/CVE-2021-47146</URL>
|
|
<URL>https://nvd.nist.gov/vuln/detail/CVE-2021-47153</URL>
|
|
<URL>https://nvd.nist.gov/vuln/detail/CVE-2021-47159</URL>
|
|
<URL>https://nvd.nist.gov/vuln/detail/CVE-2021-47160</URL>
|
|
<URL>https://nvd.nist.gov/vuln/detail/CVE-2021-47161</URL>
|
|
<URL>https://nvd.nist.gov/vuln/detail/CVE-2021-47162</URL>
|
|
<URL>https://nvd.nist.gov/vuln/detail/CVE-2021-47163</URL>
|
|
<URL>https://nvd.nist.gov/vuln/detail/CVE-2021-47167</URL>
|
|
<URL>https://nvd.nist.gov/vuln/detail/CVE-2021-47170</URL>
|
|
<URL>https://nvd.nist.gov/vuln/detail/CVE-2021-47171</URL>
|
|
<URL>https://nvd.nist.gov/vuln/detail/CVE-2021-47173</URL>
|
|
<URL>https://nvd.nist.gov/vuln/detail/CVE-2021-47180</URL>
|
|
<URL>https://nvd.nist.gov/vuln/detail/CVE-2023-52464</URL>
|
|
<URL>https://nvd.nist.gov/vuln/detail/CVE-2023-52475</URL>
|
|
<URL>https://nvd.nist.gov/vuln/detail/CVE-2023-52500</URL>
|
|
<URL>https://nvd.nist.gov/vuln/detail/CVE-2023-52507</URL>
|
|
<URL>https://nvd.nist.gov/vuln/detail/CVE-2023-52510</URL>
|
|
<URL>https://nvd.nist.gov/vuln/detail/CVE-2023-52515</URL>
|
|
<URL>https://nvd.nist.gov/vuln/detail/CVE-2023-52522</URL>
|
|
<URL>https://nvd.nist.gov/vuln/detail/CVE-2023-52530</URL>
|
|
<URL>https://nvd.nist.gov/vuln/detail/CVE-2023-52566</URL>
|
|
<URL>https://nvd.nist.gov/vuln/detail/CVE-2023-52578</URL>
|
|
<URL>https://nvd.nist.gov/vuln/detail/CVE-2023-52583</URL>
|
|
<URL>https://nvd.nist.gov/vuln/detail/CVE-2023-52587</URL>
|
|
<URL>https://nvd.nist.gov/vuln/detail/CVE-2023-52594</URL>
|
|
<URL>https://nvd.nist.gov/vuln/detail/CVE-2023-52595</URL>
|
|
<URL>https://nvd.nist.gov/vuln/detail/CVE-2023-52597</URL>
|
|
<URL>https://nvd.nist.gov/vuln/detail/CVE-2023-52598</URL>
|
|
<URL>https://nvd.nist.gov/vuln/detail/CVE-2023-52622</URL>
|
|
</Reference>
|
|
</DocumentReferences>
|
|
<ProductTree xmlns="http://www.icasi.org/CVRF/schema/prod/1.1">
|
|
<Branch Type="Product Name" Name="openEuler">
|
|
<FullProductName ProductID="openEuler-20.03-LTS-SP4" CPE="cpe:/a:openEuler:openEuler:20.03-LTS-SP4">openEuler-20.03-LTS-SP4</FullProductName>
|
|
</Branch>
|
|
<Branch Type="Package Arch" Name="aarch64">
|
|
<FullProductName ProductID="perf-debuginfo-4.19.90-2404.2.0.0273" CPE="cpe:/a:openEuler:openEuler:20.03-LTS-SP4">perf-debuginfo-4.19.90-2404.2.0.0273.oe2003sp4.aarch64.rpm</FullProductName>
|
|
<FullProductName ProductID="bpftool-4.19.90-2404.2.0.0273" CPE="cpe:/a:openEuler:openEuler:20.03-LTS-SP4">bpftool-4.19.90-2404.2.0.0273.oe2003sp4.aarch64.rpm</FullProductName>
|
|
<FullProductName ProductID="kernel-tools-devel-4.19.90-2404.2.0.0273" CPE="cpe:/a:openEuler:openEuler:20.03-LTS-SP4">kernel-tools-devel-4.19.90-2404.2.0.0273.oe2003sp4.aarch64.rpm</FullProductName>
|
|
<FullProductName ProductID="python2-perf-4.19.90-2404.2.0.0273" CPE="cpe:/a:openEuler:openEuler:20.03-LTS-SP4">python2-perf-4.19.90-2404.2.0.0273.oe2003sp4.aarch64.rpm</FullProductName>
|
|
<FullProductName ProductID="perf-4.19.90-2404.2.0.0273" CPE="cpe:/a:openEuler:openEuler:20.03-LTS-SP4">perf-4.19.90-2404.2.0.0273.oe2003sp4.aarch64.rpm</FullProductName>
|
|
<FullProductName ProductID="kernel-source-4.19.90-2404.2.0.0273" CPE="cpe:/a:openEuler:openEuler:20.03-LTS-SP4">kernel-source-4.19.90-2404.2.0.0273.oe2003sp4.aarch64.rpm</FullProductName>
|
|
<FullProductName ProductID="python3-perf-debuginfo-4.19.90-2404.2.0.0273" CPE="cpe:/a:openEuler:openEuler:20.03-LTS-SP4">python3-perf-debuginfo-4.19.90-2404.2.0.0273.oe2003sp4.aarch64.rpm</FullProductName>
|
|
<FullProductName ProductID="python3-perf-4.19.90-2404.2.0.0273" CPE="cpe:/a:openEuler:openEuler:20.03-LTS-SP4">python3-perf-4.19.90-2404.2.0.0273.oe2003sp4.aarch64.rpm</FullProductName>
|
|
<FullProductName ProductID="bpftool-debuginfo-4.19.90-2404.2.0.0273" CPE="cpe:/a:openEuler:openEuler:20.03-LTS-SP4">bpftool-debuginfo-4.19.90-2404.2.0.0273.oe2003sp4.aarch64.rpm</FullProductName>
|
|
<FullProductName ProductID="kernel-debugsource-4.19.90-2404.2.0.0273" CPE="cpe:/a:openEuler:openEuler:20.03-LTS-SP4">kernel-debugsource-4.19.90-2404.2.0.0273.oe2003sp4.aarch64.rpm</FullProductName>
|
|
<FullProductName ProductID="kernel-debuginfo-4.19.90-2404.2.0.0273" CPE="cpe:/a:openEuler:openEuler:20.03-LTS-SP4">kernel-debuginfo-4.19.90-2404.2.0.0273.oe2003sp4.aarch64.rpm</FullProductName>
|
|
<FullProductName ProductID="python2-perf-debuginfo-4.19.90-2404.2.0.0273" CPE="cpe:/a:openEuler:openEuler:20.03-LTS-SP4">python2-perf-debuginfo-4.19.90-2404.2.0.0273.oe2003sp4.aarch64.rpm</FullProductName>
|
|
<FullProductName ProductID="kernel-tools-debuginfo-4.19.90-2404.2.0.0273" CPE="cpe:/a:openEuler:openEuler:20.03-LTS-SP4">kernel-tools-debuginfo-4.19.90-2404.2.0.0273.oe2003sp4.aarch64.rpm</FullProductName>
|
|
<FullProductName ProductID="kernel-tools-4.19.90-2404.2.0.0273" CPE="cpe:/a:openEuler:openEuler:20.03-LTS-SP4">kernel-tools-4.19.90-2404.2.0.0273.oe2003sp4.aarch64.rpm</FullProductName>
|
|
<FullProductName ProductID="kernel-4.19.90-2404.2.0.0273" CPE="cpe:/a:openEuler:openEuler:20.03-LTS-SP4">kernel-4.19.90-2404.2.0.0273.oe2003sp4.aarch64.rpm</FullProductName>
|
|
<FullProductName ProductID="kernel-devel-4.19.90-2404.2.0.0273" CPE="cpe:/a:openEuler:openEuler:20.03-LTS-SP4">kernel-devel-4.19.90-2404.2.0.0273.oe2003sp4.aarch64.rpm</FullProductName>
|
|
</Branch>
|
|
<Branch Type="Package Arch" Name="src">
|
|
<FullProductName ProductID="kernel-4.19.90-2404.2.0.0273" CPE="cpe:/a:openEuler:openEuler:20.03-LTS-SP4">kernel-4.19.90-2404.2.0.0273.oe2003sp4.src.rpm</FullProductName>
|
|
</Branch>
|
|
<Branch Type="Package Arch" Name="x86_64">
|
|
<FullProductName ProductID="kernel-debugsource-4.19.90-2404.2.0.0273" CPE="cpe:/a:openEuler:openEuler:20.03-LTS-SP4">kernel-debugsource-4.19.90-2404.2.0.0273.oe2003sp4.x86_64.rpm</FullProductName>
|
|
<FullProductName ProductID="kernel-source-4.19.90-2404.2.0.0273" CPE="cpe:/a:openEuler:openEuler:20.03-LTS-SP4">kernel-source-4.19.90-2404.2.0.0273.oe2003sp4.x86_64.rpm</FullProductName>
|
|
<FullProductName ProductID="python3-perf-debuginfo-4.19.90-2404.2.0.0273" CPE="cpe:/a:openEuler:openEuler:20.03-LTS-SP4">python3-perf-debuginfo-4.19.90-2404.2.0.0273.oe2003sp4.x86_64.rpm</FullProductName>
|
|
<FullProductName ProductID="kernel-4.19.90-2404.2.0.0273" CPE="cpe:/a:openEuler:openEuler:20.03-LTS-SP4">kernel-4.19.90-2404.2.0.0273.oe2003sp4.x86_64.rpm</FullProductName>
|
|
<FullProductName ProductID="kernel-tools-4.19.90-2404.2.0.0273" CPE="cpe:/a:openEuler:openEuler:20.03-LTS-SP4">kernel-tools-4.19.90-2404.2.0.0273.oe2003sp4.x86_64.rpm</FullProductName>
|
|
<FullProductName ProductID="python2-perf-4.19.90-2404.2.0.0273" CPE="cpe:/a:openEuler:openEuler:20.03-LTS-SP4">python2-perf-4.19.90-2404.2.0.0273.oe2003sp4.x86_64.rpm</FullProductName>
|
|
<FullProductName ProductID="kernel-debuginfo-4.19.90-2404.2.0.0273" CPE="cpe:/a:openEuler:openEuler:20.03-LTS-SP4">kernel-debuginfo-4.19.90-2404.2.0.0273.oe2003sp4.x86_64.rpm</FullProductName>
|
|
<FullProductName ProductID="kernel-devel-4.19.90-2404.2.0.0273" CPE="cpe:/a:openEuler:openEuler:20.03-LTS-SP4">kernel-devel-4.19.90-2404.2.0.0273.oe2003sp4.x86_64.rpm</FullProductName>
|
|
<FullProductName ProductID="python2-perf-debuginfo-4.19.90-2404.2.0.0273" CPE="cpe:/a:openEuler:openEuler:20.03-LTS-SP4">python2-perf-debuginfo-4.19.90-2404.2.0.0273.oe2003sp4.x86_64.rpm</FullProductName>
|
|
<FullProductName ProductID="kernel-tools-debuginfo-4.19.90-2404.2.0.0273" CPE="cpe:/a:openEuler:openEuler:20.03-LTS-SP4">kernel-tools-debuginfo-4.19.90-2404.2.0.0273.oe2003sp4.x86_64.rpm</FullProductName>
|
|
<FullProductName ProductID="perf-4.19.90-2404.2.0.0273" CPE="cpe:/a:openEuler:openEuler:20.03-LTS-SP4">perf-4.19.90-2404.2.0.0273.oe2003sp4.x86_64.rpm</FullProductName>
|
|
<FullProductName ProductID="bpftool-debuginfo-4.19.90-2404.2.0.0273" CPE="cpe:/a:openEuler:openEuler:20.03-LTS-SP4">bpftool-debuginfo-4.19.90-2404.2.0.0273.oe2003sp4.x86_64.rpm</FullProductName>
|
|
<FullProductName ProductID="kernel-tools-devel-4.19.90-2404.2.0.0273" CPE="cpe:/a:openEuler:openEuler:20.03-LTS-SP4">kernel-tools-devel-4.19.90-2404.2.0.0273.oe2003sp4.x86_64.rpm</FullProductName>
|
|
<FullProductName ProductID="bpftool-4.19.90-2404.2.0.0273" CPE="cpe:/a:openEuler:openEuler:20.03-LTS-SP4">bpftool-4.19.90-2404.2.0.0273.oe2003sp4.x86_64.rpm</FullProductName>
|
|
<FullProductName ProductID="perf-debuginfo-4.19.90-2404.2.0.0273" CPE="cpe:/a:openEuler:openEuler:20.03-LTS-SP4">perf-debuginfo-4.19.90-2404.2.0.0273.oe2003sp4.x86_64.rpm</FullProductName>
|
|
<FullProductName ProductID="python3-perf-4.19.90-2404.2.0.0273" CPE="cpe:/a:openEuler:openEuler:20.03-LTS-SP4">python3-perf-4.19.90-2404.2.0.0273.oe2003sp4.x86_64.rpm</FullProductName>
|
|
</Branch>
|
|
</ProductTree>
|
|
<Vulnerability Ordinal="1" xmlns="http://www.icasi.org/CVRF/schema/vuln/1.1">
|
|
<Notes>
|
|
<Note Title="Vulnerability Description" Type="General" Ordinal="1" xml:lang="en">In the Linux kernel, the following vulnerability has been resolved:
|
|
|
|
i2c: img-scb: fix reference leak when pm_runtime_get_sync fails
|
|
|
|
The PM reference count is not expected to be incremented on
|
|
return in functions img_i2c_xfer and img_i2c_init.
|
|
|
|
However, pm_runtime_get_sync will increment the PM reference
|
|
count even failed. Forgetting to putting operation will result
|
|
in a reference leak here.
|
|
|
|
Replace it with pm_runtime_resume_and_get to keep usage
|
|
counter balanced.</Note>
|
|
</Notes>
|
|
<ReleaseDate>2024-04-19</ReleaseDate>
|
|
<CVE>CVE-2020-36783</CVE>
|
|
<ProductStatuses>
|
|
<Status Type="Fixed">
|
|
<ProductID>openEuler-20.03-LTS-SP4</ProductID>
|
|
</Status>
|
|
</ProductStatuses>
|
|
<Threats>
|
|
<Threat Type="Impact">
|
|
<Description>Medium</Description>
|
|
</Threat>
|
|
</Threats>
|
|
<CVSSScoreSets>
|
|
<ScoreSet>
|
|
<BaseScore>4.7</BaseScore>
|
|
<Vector>AV:L/AC:H/PR:L/UI:N/S:U/C:N/I:N/A:H</Vector>
|
|
</ScoreSet>
|
|
</CVSSScoreSets>
|
|
<Remediations>
|
|
<Remediation Type="Vendor Fix">
|
|
<Description>kernel security update</Description>
|
|
<DATE>2024-04-19</DATE>
|
|
<URL>https://www.openeuler.org/en/security/safety-bulletin/detail.html?id=openEuler-SA-2024-1484</URL>
|
|
</Remediation>
|
|
</Remediations>
|
|
</Vulnerability>
|
|
<Vulnerability Ordinal="2" xmlns="http://www.icasi.org/CVRF/schema/vuln/1.1">
|
|
<Notes>
|
|
<Note Title="Vulnerability Description" Type="General" Ordinal="2" xml:lang="en">In the Linux kernel, the following vulnerability has been resolved:
|
|
|
|
kyber: fix out of bounds access when preempted
|
|
|
|
__blk_mq_sched_bio_merge() gets the ctx and hctx for the current CPU and
|
|
passes the hctx to ->bio_merge(). kyber_bio_merge() then gets the ctx
|
|
for the current CPU again and uses that to get the corresponding Kyber
|
|
context in the passed hctx. However, the thread may be preempted between
|
|
the two calls to blk_mq_get_ctx(), and the ctx returned the second time
|
|
may no longer correspond to the passed hctx. This "works" accidentally
|
|
most of the time, but it can cause us to read garbage if the second ctx
|
|
came from an hctx with more ctx's than the first one (i.e., if
|
|
ctx->index_hw[hctx->type] > hctx->nr_ctx).
|
|
|
|
This manifested as this UBSAN array index out of bounds error reported
|
|
by Jakub:
|
|
|
|
UBSAN: array-index-out-of-bounds in ../kernel/locking/qspinlock.c:130:9
|
|
index 13106 is out of range for type 'long unsigned int [128]'
|
|
Call Trace:
|
|
dump_stack+0xa4/0xe5
|
|
ubsan_epilogue+0x5/0x40
|
|
__ubsan_handle_out_of_bounds.cold.13+0x2a/0x34
|
|
queued_spin_lock_slowpath+0x476/0x480
|
|
do_raw_spin_lock+0x1c2/0x1d0
|
|
kyber_bio_merge+0x112/0x180
|
|
blk_mq_submit_bio+0x1f5/0x1100
|
|
submit_bio_noacct+0x7b0/0x870
|
|
submit_bio+0xc2/0x3a0
|
|
btrfs_map_bio+0x4f0/0x9d0
|
|
btrfs_submit_data_bio+0x24e/0x310
|
|
submit_one_bio+0x7f/0xb0
|
|
submit_extent_page+0xc4/0x440
|
|
__extent_writepage_io+0x2b8/0x5e0
|
|
__extent_writepage+0x28d/0x6e0
|
|
extent_write_cache_pages+0x4d7/0x7a0
|
|
extent_writepages+0xa2/0x110
|
|
do_writepages+0x8f/0x180
|
|
__writeback_single_inode+0x99/0x7f0
|
|
writeback_sb_inodes+0x34e/0x790
|
|
__writeback_inodes_wb+0x9e/0x120
|
|
wb_writeback+0x4d2/0x660
|
|
wb_workfn+0x64d/0xa10
|
|
process_one_work+0x53a/0xa80
|
|
worker_thread+0x69/0x5b0
|
|
kthread+0x20b/0x240
|
|
ret_from_fork+0x1f/0x30
|
|
|
|
Only Kyber uses the hctx, so fix it by passing the request_queue to
|
|
->bio_merge() instead. BFQ and mq-deadline just use that, and Kyber can
|
|
map the queues itself to avoid the mismatch.</Note>
|
|
</Notes>
|
|
<ReleaseDate>2024-04-19</ReleaseDate>
|
|
<CVE>CVE-2021-46984</CVE>
|
|
<ProductStatuses>
|
|
<Status Type="Fixed">
|
|
<ProductID>openEuler-20.03-LTS-SP4</ProductID>
|
|
</Status>
|
|
</ProductStatuses>
|
|
<Threats>
|
|
<Threat Type="Impact">
|
|
<Description>Medium</Description>
|
|
</Threat>
|
|
</Threats>
|
|
<CVSSScoreSets>
|
|
<ScoreSet>
|
|
<BaseScore>6.0</BaseScore>
|
|
<Vector>AV:L/AC:L/PR:H/UI:N/S:U/C:H/I:N/A:H</Vector>
|
|
</ScoreSet>
|
|
</CVSSScoreSets>
|
|
<Remediations>
|
|
<Remediation Type="Vendor Fix">
|
|
<Description>kernel security update</Description>
|
|
<DATE>2024-04-19</DATE>
|
|
<URL>https://www.openeuler.org/en/security/safety-bulletin/detail.html?id=openEuler-SA-2024-1484</URL>
|
|
</Remediation>
|
|
</Remediations>
|
|
</Vulnerability>
|
|
<Vulnerability Ordinal="3" xmlns="http://www.icasi.org/CVRF/schema/vuln/1.1">
|
|
<Notes>
|
|
<Note Title="Vulnerability Description" Type="General" Ordinal="3" xml:lang="en">In the Linux kernel, the following vulnerability has been resolved:
|
|
|
|
bus: qcom: Put child node before return
|
|
|
|
Put child node before return to fix potential reference count leak.
|
|
Generally, the reference count of child is incremented and decremented
|
|
automatically in the macro for_each_available_child_of_node() and should
|
|
be decremented manually if the loop is broken in loop body.</Note>
|
|
</Notes>
|
|
<ReleaseDate>2024-04-19</ReleaseDate>
|
|
<CVE>CVE-2021-47054</CVE>
|
|
<ProductStatuses>
|
|
<Status Type="Fixed">
|
|
<ProductID>openEuler-20.03-LTS-SP4</ProductID>
|
|
</Status>
|
|
</ProductStatuses>
|
|
<Threats>
|
|
<Threat Type="Impact">
|
|
<Description>Low</Description>
|
|
</Threat>
|
|
</Threats>
|
|
<CVSSScoreSets>
|
|
<ScoreSet>
|
|
<BaseScore>2.3</BaseScore>
|
|
<Vector>AV:L/AC:L/PR:H/UI:N/S:U/C:N/I:N/A:L</Vector>
|
|
</ScoreSet>
|
|
</CVSSScoreSets>
|
|
<Remediations>
|
|
<Remediation Type="Vendor Fix">
|
|
<Description>kernel security update</Description>
|
|
<DATE>2024-04-19</DATE>
|
|
<URL>https://www.openeuler.org/en/security/safety-bulletin/detail.html?id=openEuler-SA-2024-1484</URL>
|
|
</Remediation>
|
|
</Remediations>
|
|
</Vulnerability>
|
|
<Vulnerability Ordinal="4" xmlns="http://www.icasi.org/CVRF/schema/vuln/1.1">
|
|
<Notes>
|
|
<Note Title="Vulnerability Description" Type="General" Ordinal="4" xml:lang="en">In the Linux kernel, the following vulnerability has been resolved:
|
|
|
|
crypto: qat - ADF_STATUS_PF_RUNNING should be set after adf_dev_init
|
|
|
|
ADF_STATUS_PF_RUNNING is (only) used and checked by adf_vf2pf_shutdown()
|
|
before calling adf_iov_putmsg()->mutex_lock(vf2pf_lock), however the
|
|
vf2pf_lock is initialized in adf_dev_init(), which can fail and when it
|
|
fail, the vf2pf_lock is either not initialized or destroyed, a subsequent
|
|
use of vf2pf_lock will cause issue.
|
|
To fix this issue, only set this flag if adf_dev_init() returns 0.
|
|
|
|
[ 7.178404] BUG: KASAN: user-memory-access in __mutex_lock.isra.0+0x1ac/0x7c0
|
|
[ 7.180345] Call Trace:
|
|
[ 7.182576] mutex_lock+0xc9/0xd0
|
|
[ 7.183257] adf_iov_putmsg+0x118/0x1a0 [intel_qat]
|
|
[ 7.183541] adf_vf2pf_shutdown+0x4d/0x7b [intel_qat]
|
|
[ 7.183834] adf_dev_shutdown+0x172/0x2b0 [intel_qat]
|
|
[ 7.184127] adf_probe+0x5e9/0x600 [qat_dh895xccvf]</Note>
|
|
</Notes>
|
|
<ReleaseDate>2024-04-19</ReleaseDate>
|
|
<CVE>CVE-2021-47056</CVE>
|
|
<ProductStatuses>
|
|
<Status Type="Fixed">
|
|
<ProductID>openEuler-20.03-LTS-SP4</ProductID>
|
|
</Status>
|
|
</ProductStatuses>
|
|
<Threats>
|
|
<Threat Type="Impact">
|
|
<Description>Medium</Description>
|
|
</Threat>
|
|
</Threats>
|
|
<CVSSScoreSets>
|
|
<ScoreSet>
|
|
<BaseScore>5.5</BaseScore>
|
|
<Vector>AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H</Vector>
|
|
</ScoreSet>
|
|
</CVSSScoreSets>
|
|
<Remediations>
|
|
<Remediation Type="Vendor Fix">
|
|
<Description>kernel security update</Description>
|
|
<DATE>2024-04-19</DATE>
|
|
<URL>https://www.openeuler.org/en/security/safety-bulletin/detail.html?id=openEuler-SA-2024-1484</URL>
|
|
</Remediation>
|
|
</Remediations>
|
|
</Vulnerability>
|
|
<Vulnerability Ordinal="5" xmlns="http://www.icasi.org/CVRF/schema/vuln/1.1">
|
|
<Notes>
|
|
<Note Title="Vulnerability Description" Type="General" Ordinal="5" xml:lang="en">In the Linux kernel, the following vulnerability has been resolved:
|
|
|
|
KVM: Stop looking for coalesced MMIO zones if the bus is destroyed
|
|
|
|
Abort the walk of coalesced MMIO zones if kvm_io_bus_unregister_dev()
|
|
fails to allocate memory for the new instance of the bus. If it can't
|
|
instantiate a new bus, unregister_dev() destroys all devices _except_ the
|
|
target device. But, it doesn't tell the caller that it obliterated the
|
|
bus and invoked the destructor for all devices that were on the bus. In
|
|
the coalesced MMIO case, this can result in a deleted list entry
|
|
dereference due to attempting to continue iterating on coalesced_zones
|
|
after future entries (in the walk) have been deleted.
|
|
|
|
Opportunistically add curly braces to the for-loop, which encompasses
|
|
many lines but sneaks by without braces due to the guts being a single
|
|
if statement.</Note>
|
|
</Notes>
|
|
<ReleaseDate>2024-04-19</ReleaseDate>
|
|
<CVE>CVE-2021-47060</CVE>
|
|
<ProductStatuses>
|
|
<Status Type="Fixed">
|
|
<ProductID>openEuler-20.03-LTS-SP4</ProductID>
|
|
</Status>
|
|
</ProductStatuses>
|
|
<Threats>
|
|
<Threat Type="Impact">
|
|
<Description>Medium</Description>
|
|
</Threat>
|
|
</Threats>
|
|
<CVSSScoreSets>
|
|
<ScoreSet>
|
|
<BaseScore>6.7</BaseScore>
|
|
<Vector>AV:L/AC:L/PR:H/UI:N/S:U/C:H/I:H/A:H</Vector>
|
|
</ScoreSet>
|
|
</CVSSScoreSets>
|
|
<Remediations>
|
|
<Remediation Type="Vendor Fix">
|
|
<Description>kernel security update</Description>
|
|
<DATE>2024-04-19</DATE>
|
|
<URL>https://www.openeuler.org/en/security/safety-bulletin/detail.html?id=openEuler-SA-2024-1484</URL>
|
|
</Remediation>
|
|
</Remediations>
|
|
</Vulnerability>
|
|
<Vulnerability Ordinal="6" xmlns="http://www.icasi.org/CVRF/schema/vuln/1.1">
|
|
<Notes>
|
|
<Note Title="Vulnerability Description" Type="General" Ordinal="6" xml:lang="en">In the Linux kernel, the following vulnerability has been resolved:
|
|
|
|
KVM: Destroy I/O bus devices on unregister failure _after_ sync'ing SRCU
|
|
|
|
If allocating a new instance of an I/O bus fails when unregistering a
|
|
device, wait to destroy the device until after all readers are guaranteed
|
|
to see the new null bus. Destroying devices before the bus is nullified
|
|
could lead to use-after-free since readers expect the devices on their
|
|
reference of the bus to remain valid.</Note>
|
|
</Notes>
|
|
<ReleaseDate>2024-04-19</ReleaseDate>
|
|
<CVE>CVE-2021-47061</CVE>
|
|
<ProductStatuses>
|
|
<Status Type="Fixed">
|
|
<ProductID>openEuler-20.03-LTS-SP4</ProductID>
|
|
</Status>
|
|
</ProductStatuses>
|
|
<Threats>
|
|
<Threat Type="Impact">
|
|
<Description>Medium</Description>
|
|
</Threat>
|
|
</Threats>
|
|
<CVSSScoreSets>
|
|
<ScoreSet>
|
|
<BaseScore>6.7</BaseScore>
|
|
<Vector>AV:L/AC:L/PR:H/UI:N/S:U/C:H/I:H/A:H</Vector>
|
|
</ScoreSet>
|
|
</CVSSScoreSets>
|
|
<Remediations>
|
|
<Remediation Type="Vendor Fix">
|
|
<Description>kernel security update</Description>
|
|
<DATE>2024-04-19</DATE>
|
|
<URL>https://www.openeuler.org/en/security/safety-bulletin/detail.html?id=openEuler-SA-2024-1484</URL>
|
|
</Remediation>
|
|
</Remediations>
|
|
</Vulnerability>
|
|
<Vulnerability Ordinal="7" xmlns="http://www.icasi.org/CVRF/schema/vuln/1.1">
|
|
<Notes>
|
|
<Note Title="Vulnerability Description" Type="General" Ordinal="7" xml:lang="en">In the Linux kernel, the following vulnerability has been resolved:
|
|
|
|
drm: bridge/panel: Cleanup connector on bridge detach
|
|
|
|
If we don't call drm_connector_cleanup() manually in
|
|
panel_bridge_detach(), the connector will be cleaned up with the other
|
|
DRM objects in the call to drm_mode_config_cleanup(). However, since our
|
|
drm_connector is devm-allocated, by the time drm_mode_config_cleanup()
|
|
will be called, our connector will be long gone. Therefore, the
|
|
connector must be cleaned up when the bridge is detached to avoid
|
|
use-after-free conditions.
|
|
|
|
v2: Cleanup connector only if it was created
|
|
|
|
v3: Add FIXME
|
|
|
|
v4: (Use connector->dev) directly in if() block</Note>
|
|
</Notes>
|
|
<ReleaseDate>2024-04-19</ReleaseDate>
|
|
<CVE>CVE-2021-47063</CVE>
|
|
<ProductStatuses>
|
|
<Status Type="Fixed">
|
|
<ProductID>openEuler-20.03-LTS-SP4</ProductID>
|
|
</Status>
|
|
</ProductStatuses>
|
|
<Threats>
|
|
<Threat Type="Impact">
|
|
<Description>Medium</Description>
|
|
</Threat>
|
|
</Threats>
|
|
<CVSSScoreSets>
|
|
<ScoreSet>
|
|
<BaseScore>6.7</BaseScore>
|
|
<Vector>AV:L/AC:L/PR:H/UI:N/S:U/C:H/I:H/A:H</Vector>
|
|
</ScoreSet>
|
|
</CVSSScoreSets>
|
|
<Remediations>
|
|
<Remediation Type="Vendor Fix">
|
|
<Description>kernel security update</Description>
|
|
<DATE>2024-04-19</DATE>
|
|
<URL>https://www.openeuler.org/en/security/safety-bulletin/detail.html?id=openEuler-SA-2024-1484</URL>
|
|
</Remediation>
|
|
</Remediations>
|
|
</Vulnerability>
|
|
<Vulnerability Ordinal="8" xmlns="http://www.icasi.org/CVRF/schema/vuln/1.1">
|
|
<Notes>
|
|
<Note Title="Vulnerability Description" Type="General" Ordinal="8" xml:lang="en">In the Linux kernel, the following vulnerability has been resolved:
|
|
|
|
uio_hv_generic: Fix a memory leak in error handling paths
|
|
|
|
If 'vmbus_establish_gpadl()' fails, the (recv|send)_gpadl will not be
|
|
updated and 'hv_uio_cleanup()' in the error handling path will not be
|
|
able to free the corresponding buffer.
|
|
|
|
In such a case, we need to free the buffer explicitly.</Note>
|
|
</Notes>
|
|
<ReleaseDate>2024-04-19</ReleaseDate>
|
|
<CVE>CVE-2021-47071</CVE>
|
|
<ProductStatuses>
|
|
<Status Type="Fixed">
|
|
<ProductID>openEuler-20.03-LTS-SP4</ProductID>
|
|
</Status>
|
|
</ProductStatuses>
|
|
<Threats>
|
|
<Threat Type="Impact">
|
|
<Description>Medium</Description>
|
|
</Threat>
|
|
</Threats>
|
|
<CVSSScoreSets>
|
|
<ScoreSet>
|
|
<BaseScore>5.5</BaseScore>
|
|
<Vector>AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N</Vector>
|
|
</ScoreSet>
|
|
</CVSSScoreSets>
|
|
<Remediations>
|
|
<Remediation Type="Vendor Fix">
|
|
<Description>kernel security update</Description>
|
|
<DATE>2024-04-19</DATE>
|
|
<URL>https://www.openeuler.org/en/security/safety-bulletin/detail.html?id=openEuler-SA-2024-1484</URL>
|
|
</Remediation>
|
|
</Remediations>
|
|
</Vulnerability>
|
|
<Vulnerability Ordinal="9" xmlns="http://www.icasi.org/CVRF/schema/vuln/1.1">
|
|
<Notes>
|
|
<Note Title="Vulnerability Description" Type="General" Ordinal="9" xml:lang="en">In the Linux kernel, the following vulnerability has been resolved:
|
|
|
|
nvme-loop: fix memory leak in nvme_loop_create_ctrl()
|
|
|
|
When creating loop ctrl in nvme_loop_create_ctrl(), if nvme_init_ctrl()
|
|
fails, the loop ctrl should be freed before jumping to the "out" label.</Note>
|
|
</Notes>
|
|
<ReleaseDate>2024-04-19</ReleaseDate>
|
|
<CVE>CVE-2021-47074</CVE>
|
|
<ProductStatuses>
|
|
<Status Type="Fixed">
|
|
<ProductID>openEuler-20.03-LTS-SP4</ProductID>
|
|
</Status>
|
|
</ProductStatuses>
|
|
<Threats>
|
|
<Threat Type="Impact">
|
|
<Description>Medium</Description>
|
|
</Threat>
|
|
</Threats>
|
|
<CVSSScoreSets>
|
|
<ScoreSet>
|
|
<BaseScore>5.5</BaseScore>
|
|
<Vector>AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H</Vector>
|
|
</ScoreSet>
|
|
</CVSSScoreSets>
|
|
<Remediations>
|
|
<Remediation Type="Vendor Fix">
|
|
<Description>kernel security update</Description>
|
|
<DATE>2024-04-19</DATE>
|
|
<URL>https://www.openeuler.org/en/security/safety-bulletin/detail.html?id=openEuler-SA-2024-1484</URL>
|
|
</Remediation>
|
|
</Remediations>
|
|
</Vulnerability>
|
|
<Vulnerability Ordinal="10" xmlns="http://www.icasi.org/CVRF/schema/vuln/1.1">
|
|
<Notes>
|
|
<Note Title="Vulnerability Description" Type="General" Ordinal="10" xml:lang="en">In the Linux kernel, the following vulnerability has been resolved:
|
|
|
|
scsi: qedf: Add pointer checks in qedf_update_link_speed()
|
|
|
|
The following trace was observed:
|
|
|
|
[ 14.042059] Call Trace:
|
|
[ 14.042061] <IRQ>
|
|
[ 14.042068] qedf_link_update+0x144/0x1f0 [qedf]
|
|
[ 14.042117] qed_link_update+0x5c/0x80 [qed]
|
|
[ 14.042135] qed_mcp_handle_link_change+0x2d2/0x410 [qed]
|
|
[ 14.042155] ? qed_set_ptt+0x70/0x80 [qed]
|
|
[ 14.042170] ? qed_set_ptt+0x70/0x80 [qed]
|
|
[ 14.042186] ? qed_rd+0x13/0x40 [qed]
|
|
[ 14.042205] qed_mcp_handle_events+0x437/0x690 [qed]
|
|
[ 14.042221] ? qed_set_ptt+0x70/0x80 [qed]
|
|
[ 14.042239] qed_int_sp_dpc+0x3a6/0x3e0 [qed]
|
|
[ 14.042245] tasklet_action_common.isra.14+0x5a/0x100
|
|
[ 14.042250] __do_softirq+0xe4/0x2f8
|
|
[ 14.042253] irq_exit+0xf7/0x100
|
|
[ 14.042255] do_IRQ+0x7f/0xd0
|
|
[ 14.042257] common_interrupt+0xf/0xf
|
|
[ 14.042259] </IRQ>
|
|
|
|
API qedf_link_update() is getting called from QED but by that time
|
|
shost_data is not initialised. This results in a NULL pointer dereference
|
|
when we try to dereference shost_data while updating supported_speeds.
|
|
|
|
Add a NULL pointer check before dereferencing shost_data.</Note>
|
|
</Notes>
|
|
<ReleaseDate>2024-04-19</ReleaseDate>
|
|
<CVE>CVE-2021-47077</CVE>
|
|
<ProductStatuses>
|
|
<Status Type="Fixed">
|
|
<ProductID>openEuler-20.03-LTS-SP4</ProductID>
|
|
</Status>
|
|
</ProductStatuses>
|
|
<Threats>
|
|
<Threat Type="Impact">
|
|
<Description>Medium</Description>
|
|
</Threat>
|
|
</Threats>
|
|
<CVSSScoreSets>
|
|
<ScoreSet>
|
|
<BaseScore>5.5</BaseScore>
|
|
<Vector>AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H</Vector>
|
|
</ScoreSet>
|
|
</CVSSScoreSets>
|
|
<Remediations>
|
|
<Remediation Type="Vendor Fix">
|
|
<Description>kernel security update</Description>
|
|
<DATE>2024-04-19</DATE>
|
|
<URL>https://www.openeuler.org/en/security/safety-bulletin/detail.html?id=openEuler-SA-2024-1484</URL>
|
|
</Remediation>
|
|
</Remediations>
|
|
</Vulnerability>
|
|
<Vulnerability Ordinal="11" xmlns="http://www.icasi.org/CVRF/schema/vuln/1.1">
|
|
<Notes>
|
|
<Note Title="Vulnerability Description" Type="General" Ordinal="11" xml:lang="en">In the Linux kernel, the following vulnerability has been resolved:
|
|
|
|
RDMA/rxe: Clear all QP fields if creation failed
|
|
|
|
rxe_qp_do_cleanup() relies on valid pointer values in QP for the properly
|
|
created ones, but in case rxe_qp_from_init() failed it was filled with
|
|
garbage and caused tot the following error.
|
|
|
|
refcount_t: underflow; use-after-free.
|
|
WARNING: CPU: 1 PID: 12560 at lib/refcount.c:28 refcount_warn_saturate+0x1d1/0x1e0 lib/refcount.c:28
|
|
Modules linked in:
|
|
CPU: 1 PID: 12560 Comm: syz-executor.4 Not tainted 5.12.0-syzkaller #0
|
|
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 01/01/2011
|
|
RIP: 0010:refcount_warn_saturate+0x1d1/0x1e0 lib/refcount.c:28
|
|
Code: e9 db fe ff ff 48 89 df e8 2c c2 ea fd e9 8a fe ff ff e8 72 6a a7 fd 48 c7 c7 e0 b2 c1 89 c6 05 dc 3a e6 09 01 e8 ee 74 fb 04 <0f> 0b e9 af fe ff ff 0f 1f 84 00 00 00 00 00 41 56 41 55 41 54 55
|
|
RSP: 0018:ffffc900097ceba8 EFLAGS: 00010286
|
|
RAX: 0000000000000000 RBX: 0000000000000000 RCX: 0000000000000000
|
|
RDX: 0000000000040000 RSI: ffffffff815bb075 RDI: fffff520012f9d67
|
|
RBP: 0000000000000003 R08: 0000000000000000 R09: 0000000000000000
|
|
R10: ffffffff815b4eae R11: 0000000000000000 R12: ffff8880322a4800
|
|
R13: ffff8880322a4940 R14: ffff888033044e00 R15: 0000000000000000
|
|
FS: 00007f6eb2be3700(0000) GS:ffff8880b9d00000(0000) knlGS:0000000000000000
|
|
CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
|
|
CR2: 00007fdbe5d41000 CR3: 000000001d181000 CR4: 00000000001506e0
|
|
DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000
|
|
DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400
|
|
Call Trace:
|
|
__refcount_sub_and_test include/linux/refcount.h:283 [inline]
|
|
__refcount_dec_and_test include/linux/refcount.h:315 [inline]
|
|
refcount_dec_and_test include/linux/refcount.h:333 [inline]
|
|
kref_put include/linux/kref.h:64 [inline]
|
|
rxe_qp_do_cleanup+0x96f/0xaf0 drivers/infiniband/sw/rxe/rxe_qp.c:805
|
|
execute_in_process_context+0x37/0x150 kernel/workqueue.c:3327
|
|
rxe_elem_release+0x9f/0x180 drivers/infiniband/sw/rxe/rxe_pool.c:391
|
|
kref_put include/linux/kref.h:65 [inline]
|
|
rxe_create_qp+0x2cd/0x310 drivers/infiniband/sw/rxe/rxe_verbs.c:425
|
|
_ib_create_qp drivers/infiniband/core/core_priv.h:331 [inline]
|
|
ib_create_named_qp+0x2ad/0x1370 drivers/infiniband/core/verbs.c:1231
|
|
ib_create_qp include/rdma/ib_verbs.h:3644 [inline]
|
|
create_mad_qp+0x177/0x2d0 drivers/infiniband/core/mad.c:2920
|
|
ib_mad_port_open drivers/infiniband/core/mad.c:3001 [inline]
|
|
ib_mad_init_device+0xd6f/0x1400 drivers/infiniband/core/mad.c:3092
|
|
add_client_context+0x405/0x5e0 drivers/infiniband/core/device.c:717
|
|
enable_device_and_get+0x1cd/0x3b0 drivers/infiniband/core/device.c:1331
|
|
ib_register_device drivers/infiniband/core/device.c:1413 [inline]
|
|
ib_register_device+0x7c7/0xa50 drivers/infiniband/core/device.c:1365
|
|
rxe_register_device+0x3d5/0x4a0 drivers/infiniband/sw/rxe/rxe_verbs.c:1147
|
|
rxe_add+0x12fe/0x16d0 drivers/infiniband/sw/rxe/rxe.c:247
|
|
rxe_net_add+0x8c/0xe0 drivers/infiniband/sw/rxe/rxe_net.c:503
|
|
rxe_newlink drivers/infiniband/sw/rxe/rxe.c:269 [inline]
|
|
rxe_newlink+0xb7/0xe0 drivers/infiniband/sw/rxe/rxe.c:250
|
|
nldev_newlink+0x30e/0x550 drivers/infiniband/core/nldev.c:1555
|
|
rdma_nl_rcv_msg+0x36d/0x690 drivers/infiniband/core/netlink.c:195
|
|
rdma_nl_rcv_skb drivers/infiniband/core/netlink.c:239 [inline]
|
|
rdma_nl_rcv+0x2ee/0x430 drivers/infiniband/core/netlink.c:259
|
|
netlink_unicast_kernel net/netlink/af_netlink.c:1312 [inline]
|
|
netlink_unicast+0x533/0x7d0 net/netlink/af_netlink.c:1338
|
|
netlink_sendmsg+0x856/0xd90 net/netlink/af_netlink.c:1927
|
|
sock_sendmsg_nosec net/socket.c:654 [inline]
|
|
sock_sendmsg+0xcf/0x120 net/socket.c:674
|
|
____sys_sendmsg+0x6e8/0x810 net/socket.c:2350
|
|
___sys_sendmsg+0xf3/0x170 net/socket.c:2404
|
|
__sys_sendmsg+0xe5/0x1b0 net/socket.c:2433
|
|
do_syscall_64+0x3a/0xb0 arch/x86/entry/common.c:47
|
|
entry_SYSCALL_64_after_hwframe+0
|
|
---truncated---</Note>
|
|
</Notes>
|
|
<ReleaseDate>2024-04-19</ReleaseDate>
|
|
<CVE>CVE-2021-47078</CVE>
|
|
<ProductStatuses>
|
|
<Status Type="Fixed">
|
|
<ProductID>openEuler-20.03-LTS-SP4</ProductID>
|
|
</Status>
|
|
</ProductStatuses>
|
|
<Threats>
|
|
<Threat Type="Impact">
|
|
<Description>Medium</Description>
|
|
</Threat>
|
|
</Threats>
|
|
<CVSSScoreSets>
|
|
<ScoreSet>
|
|
<BaseScore>5.3</BaseScore>
|
|
<Vector>AV:L/AC:L/PR:L/UI:N/S:U/C:L/I:L/A:L</Vector>
|
|
</ScoreSet>
|
|
</CVSSScoreSets>
|
|
<Remediations>
|
|
<Remediation Type="Vendor Fix">
|
|
<Description>kernel security update</Description>
|
|
<DATE>2024-04-19</DATE>
|
|
<URL>https://www.openeuler.org/en/security/safety-bulletin/detail.html?id=openEuler-SA-2024-1484</URL>
|
|
</Remediation>
|
|
</Remediations>
|
|
</Vulnerability>
|
|
<Vulnerability Ordinal="12" xmlns="http://www.icasi.org/CVRF/schema/vuln/1.1">
|
|
<Notes>
|
|
<Note Title="Vulnerability Description" Type="General" Ordinal="12" xml:lang="en">In the Linux kernel, the following vulnerability has been resolved:
|
|
|
|
asix: fix uninit-value in asix_mdio_read()
|
|
|
|
asix_read_cmd() may read less than sizeof(smsr) bytes and in this case
|
|
smsr will be uninitialized.
|
|
|
|
Fail log:
|
|
BUG: KMSAN: uninit-value in asix_check_host_enable drivers/net/usb/asix_common.c:82 [inline]
|
|
BUG: KMSAN: uninit-value in asix_check_host_enable drivers/net/usb/asix_common.c:82 [inline] drivers/net/usb/asix_common.c:497
|
|
BUG: KMSAN: uninit-value in asix_mdio_read+0x3c1/0xb00 drivers/net/usb/asix_common.c:497 drivers/net/usb/asix_common.c:497
|
|
asix_check_host_enable drivers/net/usb/asix_common.c:82 [inline]
|
|
asix_check_host_enable drivers/net/usb/asix_common.c:82 [inline] drivers/net/usb/asix_common.c:497
|
|
asix_mdio_read+0x3c1/0xb00 drivers/net/usb/asix_common.c:497 drivers/net/usb/asix_common.c:497</Note>
|
|
</Notes>
|
|
<ReleaseDate>2024-04-19</ReleaseDate>
|
|
<CVE>CVE-2021-47101</CVE>
|
|
<ProductStatuses>
|
|
<Status Type="Fixed">
|
|
<ProductID>openEuler-20.03-LTS-SP4</ProductID>
|
|
</Status>
|
|
</ProductStatuses>
|
|
<Threats>
|
|
<Threat Type="Impact">
|
|
<Description>Low</Description>
|
|
</Threat>
|
|
</Threats>
|
|
<CVSSScoreSets>
|
|
<ScoreSet>
|
|
<BaseScore>4.0</BaseScore>
|
|
<Vector>AV:L/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N</Vector>
|
|
</ScoreSet>
|
|
</CVSSScoreSets>
|
|
<Remediations>
|
|
<Remediation Type="Vendor Fix">
|
|
<Description>kernel security update</Description>
|
|
<DATE>2024-04-19</DATE>
|
|
<URL>https://www.openeuler.org/en/security/safety-bulletin/detail.html?id=openEuler-SA-2024-1484</URL>
|
|
</Remediation>
|
|
</Remediations>
|
|
</Vulnerability>
|
|
<Vulnerability Ordinal="13" xmlns="http://www.icasi.org/CVRF/schema/vuln/1.1">
|
|
<Notes>
|
|
<Note Title="Vulnerability Description" Type="General" Ordinal="13" xml:lang="en">In the Linux kernel, the following vulnerability has been resolved:
|
|
|
|
net/tls: Fix use-after-free after the TLS device goes down and up
|
|
|
|
When a netdev with active TLS offload goes down, tls_device_down is
|
|
called to stop the offload and tear down the TLS context. However, the
|
|
socket stays alive, and it still points to the TLS context, which is now
|
|
deallocated. If a netdev goes up, while the connection is still active,
|
|
and the data flow resumes after a number of TCP retransmissions, it will
|
|
lead to a use-after-free of the TLS context.
|
|
|
|
This commit addresses this bug by keeping the context alive until its
|
|
normal destruction, and implements the necessary fallbacks, so that the
|
|
connection can resume in software (non-offloaded) kTLS mode.
|
|
|
|
On the TX side tls_sw_fallback is used to encrypt all packets. The RX
|
|
side already has all the necessary fallbacks, because receiving
|
|
non-decrypted packets is supported. The thing needed on the RX side is
|
|
to block resync requests, which are normally produced after receiving
|
|
non-decrypted packets.
|
|
|
|
The necessary synchronization is implemented for a graceful teardown:
|
|
first the fallbacks are deployed, then the driver resources are released
|
|
(it used to be possible to have a tls_dev_resync after tls_dev_del).
|
|
|
|
A new flag called TLS_RX_DEV_DEGRADED is added to indicate the fallback
|
|
mode. It's used to skip the RX resync logic completely, as it becomes
|
|
useless, and some objects may be released (for example, resync_async,
|
|
which is allocated and freed by the driver).</Note>
|
|
</Notes>
|
|
<ReleaseDate>2024-04-19</ReleaseDate>
|
|
<CVE>CVE-2021-47131</CVE>
|
|
<ProductStatuses>
|
|
<Status Type="Fixed">
|
|
<ProductID>openEuler-20.03-LTS-SP4</ProductID>
|
|
</Status>
|
|
</ProductStatuses>
|
|
<Threats>
|
|
<Threat Type="Impact">
|
|
<Description>High</Description>
|
|
</Threat>
|
|
</Threats>
|
|
<CVSSScoreSets>
|
|
<ScoreSet>
|
|
<BaseScore>7.8</BaseScore>
|
|
<Vector>AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H</Vector>
|
|
</ScoreSet>
|
|
</CVSSScoreSets>
|
|
<Remediations>
|
|
<Remediation Type="Vendor Fix">
|
|
<Description>kernel security update</Description>
|
|
<DATE>2024-04-19</DATE>
|
|
<URL>https://www.openeuler.org/en/security/safety-bulletin/detail.html?id=openEuler-SA-2024-1484</URL>
|
|
</Remediation>
|
|
</Remediations>
|
|
</Vulnerability>
|
|
<Vulnerability Ordinal="14" xmlns="http://www.icasi.org/CVRF/schema/vuln/1.1">
|
|
<Notes>
|
|
<Note Title="Vulnerability Description" Type="General" Ordinal="14" xml:lang="en">In the Linux kernel, the following vulnerability has been resolved:
|
|
|
|
drm/amdgpu: Fix a use-after-free
|
|
|
|
looks like we forget to set ttm->sg to NULL.
|
|
Hit panic below
|
|
|
|
[ 1235.844104] general protection fault, probably for non-canonical address 0x6b6b6b6b6b6b7b4b: 0000 [#1] SMP DEBUG_PAGEALLOC NOPTI
|
|
[ 1235.989074] Call Trace:
|
|
[ 1235.991751] sg_free_table+0x17/0x20
|
|
[ 1235.995667] amdgpu_ttm_backend_unbind.cold+0x4d/0xf7 [amdgpu]
|
|
[ 1236.002288] amdgpu_ttm_backend_destroy+0x29/0x130 [amdgpu]
|
|
[ 1236.008464] ttm_tt_destroy+0x1e/0x30 [ttm]
|
|
[ 1236.013066] ttm_bo_cleanup_memtype_use+0x51/0xa0 [ttm]
|
|
[ 1236.018783] ttm_bo_release+0x262/0xa50 [ttm]
|
|
[ 1236.023547] ttm_bo_put+0x82/0xd0 [ttm]
|
|
[ 1236.027766] amdgpu_bo_unref+0x26/0x50 [amdgpu]
|
|
[ 1236.032809] amdgpu_amdkfd_gpuvm_alloc_memory_of_gpu+0x7aa/0xd90 [amdgpu]
|
|
[ 1236.040400] kfd_ioctl_alloc_memory_of_gpu+0xe2/0x330 [amdgpu]
|
|
[ 1236.046912] kfd_ioctl+0x463/0x690 [amdgpu]</Note>
|
|
</Notes>
|
|
<ReleaseDate>2024-04-19</ReleaseDate>
|
|
<CVE>CVE-2021-47142</CVE>
|
|
<ProductStatuses>
|
|
<Status Type="Fixed">
|
|
<ProductID>openEuler-20.03-LTS-SP4</ProductID>
|
|
</Status>
|
|
</ProductStatuses>
|
|
<Threats>
|
|
<Threat Type="Impact">
|
|
<Description>Medium</Description>
|
|
</Threat>
|
|
</Threats>
|
|
<CVSSScoreSets>
|
|
<ScoreSet>
|
|
<BaseScore>5.5</BaseScore>
|
|
<Vector>AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H</Vector>
|
|
</ScoreSet>
|
|
</CVSSScoreSets>
|
|
<Remediations>
|
|
<Remediation Type="Vendor Fix">
|
|
<Description>kernel security update</Description>
|
|
<DATE>2024-04-19</DATE>
|
|
<URL>https://www.openeuler.org/en/security/safety-bulletin/detail.html?id=openEuler-SA-2024-1484</URL>
|
|
</Remediation>
|
|
</Remediations>
|
|
</Vulnerability>
|
|
<Vulnerability Ordinal="15" xmlns="http://www.icasi.org/CVRF/schema/vuln/1.1">
|
|
<Notes>
|
|
<Note Title="Vulnerability Description" Type="General" Ordinal="15" xml:lang="en">In the Linux kernel, the following vulnerability has been resolved:
|
|
|
|
net/smc: remove device from smcd_dev_list after failed device_add()
|
|
|
|
If the device_add() for a smcd_dev fails, there's no cleanup step that
|
|
rolls back the earlier list_add(). The device subsequently gets freed,
|
|
and we end up with a corrupted list.
|
|
|
|
Add some error handling that removes the device from the list.</Note>
|
|
</Notes>
|
|
<ReleaseDate>2024-04-19</ReleaseDate>
|
|
<CVE>CVE-2021-47143</CVE>
|
|
<ProductStatuses>
|
|
<Status Type="Fixed">
|
|
<ProductID>openEuler-20.03-LTS-SP4</ProductID>
|
|
</Status>
|
|
</ProductStatuses>
|
|
<Threats>
|
|
<Threat Type="Impact">
|
|
<Description>Medium</Description>
|
|
</Threat>
|
|
</Threats>
|
|
<CVSSScoreSets>
|
|
<ScoreSet>
|
|
<BaseScore>5.5</BaseScore>
|
|
<Vector>AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H</Vector>
|
|
</ScoreSet>
|
|
</CVSSScoreSets>
|
|
<Remediations>
|
|
<Remediation Type="Vendor Fix">
|
|
<Description>kernel security update</Description>
|
|
<DATE>2024-04-19</DATE>
|
|
<URL>https://www.openeuler.org/en/security/safety-bulletin/detail.html?id=openEuler-SA-2024-1484</URL>
|
|
</Remediation>
|
|
</Remediations>
|
|
</Vulnerability>
|
|
<Vulnerability Ordinal="16" xmlns="http://www.icasi.org/CVRF/schema/vuln/1.1">
|
|
<Notes>
|
|
<Note Title="Vulnerability Description" Type="General" Ordinal="16" xml:lang="en">In the Linux kernel, the following vulnerability has been resolved:
|
|
|
|
drm/amd/amdgpu: fix refcount leak
|
|
|
|
[Why]
|
|
the gem object rfb->base.obj[0] is get according to num_planes
|
|
in amdgpufb_create, but is not put according to num_planes
|
|
|
|
[How]
|
|
put rfb->base.obj[0] in amdgpu_fbdev_destroy according to num_planes</Note>
|
|
</Notes>
|
|
<ReleaseDate>2024-04-19</ReleaseDate>
|
|
<CVE>CVE-2021-47144</CVE>
|
|
<ProductStatuses>
|
|
<Status Type="Fixed">
|
|
<ProductID>openEuler-20.03-LTS-SP4</ProductID>
|
|
</Status>
|
|
</ProductStatuses>
|
|
<Threats>
|
|
<Threat Type="Impact">
|
|
<Description>Medium</Description>
|
|
</Threat>
|
|
</Threats>
|
|
<CVSSScoreSets>
|
|
<ScoreSet>
|
|
<BaseScore>5.5</BaseScore>
|
|
<Vector>AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H</Vector>
|
|
</ScoreSet>
|
|
</CVSSScoreSets>
|
|
<Remediations>
|
|
<Remediation Type="Vendor Fix">
|
|
<Description>kernel security update</Description>
|
|
<DATE>2024-04-19</DATE>
|
|
<URL>https://www.openeuler.org/en/security/safety-bulletin/detail.html?id=openEuler-SA-2024-1484</URL>
|
|
</Remediation>
|
|
</Remediations>
|
|
</Vulnerability>
|
|
<Vulnerability Ordinal="17" xmlns="http://www.icasi.org/CVRF/schema/vuln/1.1">
|
|
<Notes>
|
|
<Note Title="Vulnerability Description" Type="General" Ordinal="17" xml:lang="en">In the Linux kernel, the following vulnerability has been resolved:
|
|
|
|
btrfs: do not BUG_ON in link_to_fixup_dir
|
|
|
|
While doing error injection testing I got the following panic
|
|
|
|
kernel BUG at fs/btrfs/tree-log.c:1862!
|
|
invalid opcode: 0000 [#1] SMP NOPTI
|
|
CPU: 1 PID: 7836 Comm: mount Not tainted 5.13.0-rc1+ #305
|
|
Hardware name: QEMU Standard PC (Q35 + ICH9, 2009), BIOS 1.13.0-2.fc32 04/01/2014
|
|
RIP: 0010:link_to_fixup_dir+0xd5/0xe0
|
|
RSP: 0018:ffffb5800180fa30 EFLAGS: 00010216
|
|
RAX: fffffffffffffffb RBX: 00000000fffffffb RCX: ffff8f595287faf0
|
|
RDX: ffffb5800180fa37 RSI: ffff8f5954978800 RDI: 0000000000000000
|
|
RBP: ffff8f5953af9450 R08: 0000000000000019 R09: 0000000000000001
|
|
R10: 000151f408682970 R11: 0000000120021001 R12: ffff8f5954978800
|
|
R13: ffff8f595287faf0 R14: ffff8f5953c77dd0 R15: 0000000000000065
|
|
FS: 00007fc5284c8c40(0000) GS:ffff8f59bbd00000(0000) knlGS:0000000000000000
|
|
CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
|
|
CR2: 00007fc5287f47c0 CR3: 000000011275e002 CR4: 0000000000370ee0
|
|
Call Trace:
|
|
replay_one_buffer+0x409/0x470
|
|
? btree_read_extent_buffer_pages+0xd0/0x110
|
|
walk_up_log_tree+0x157/0x1e0
|
|
walk_log_tree+0xa6/0x1d0
|
|
btrfs_recover_log_trees+0x1da/0x360
|
|
? replay_one_extent+0x7b0/0x7b0
|
|
open_ctree+0x1486/0x1720
|
|
btrfs_mount_root.cold+0x12/0xea
|
|
? __kmalloc_track_caller+0x12f/0x240
|
|
legacy_get_tree+0x24/0x40
|
|
vfs_get_tree+0x22/0xb0
|
|
vfs_kern_mount.part.0+0x71/0xb0
|
|
btrfs_mount+0x10d/0x380
|
|
? vfs_parse_fs_string+0x4d/0x90
|
|
legacy_get_tree+0x24/0x40
|
|
vfs_get_tree+0x22/0xb0
|
|
path_mount+0x433/0xa10
|
|
__x64_sys_mount+0xe3/0x120
|
|
do_syscall_64+0x3d/0x80
|
|
entry_SYSCALL_64_after_hwframe+0x44/0xae
|
|
|
|
We can get -EIO or any number of legitimate errors from
|
|
btrfs_search_slot(), panicing here is not the appropriate response. The
|
|
error path for this code handles errors properly, simply return the
|
|
error.</Note>
|
|
</Notes>
|
|
<ReleaseDate>2024-04-19</ReleaseDate>
|
|
<CVE>CVE-2021-47145</CVE>
|
|
<ProductStatuses>
|
|
<Status Type="Fixed">
|
|
<ProductID>openEuler-20.03-LTS-SP4</ProductID>
|
|
</Status>
|
|
</ProductStatuses>
|
|
<Threats>
|
|
<Threat Type="Impact">
|
|
<Description>Medium</Description>
|
|
</Threat>
|
|
</Threats>
|
|
<CVSSScoreSets>
|
|
<ScoreSet>
|
|
<BaseScore>5.5</BaseScore>
|
|
<Vector>AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H</Vector>
|
|
</ScoreSet>
|
|
</CVSSScoreSets>
|
|
<Remediations>
|
|
<Remediation Type="Vendor Fix">
|
|
<Description>kernel security update</Description>
|
|
<DATE>2024-04-19</DATE>
|
|
<URL>https://www.openeuler.org/en/security/safety-bulletin/detail.html?id=openEuler-SA-2024-1484</URL>
|
|
</Remediation>
|
|
</Remediations>
|
|
</Vulnerability>
|
|
<Vulnerability Ordinal="18" xmlns="http://www.icasi.org/CVRF/schema/vuln/1.1">
|
|
<Notes>
|
|
<Note Title="Vulnerability Description" Type="General" Ordinal="18" xml:lang="en">In the Linux kernel, the following vulnerability has been resolved:
|
|
|
|
mld: fix panic in mld_newpack()
|
|
|
|
mld_newpack() doesn't allow to allocate high order page,
|
|
only order-0 allocation is allowed.
|
|
If headroom size is too large, a kernel panic could occur in skb_put().
|
|
|
|
Test commands:
|
|
ip netns del A
|
|
ip netns del B
|
|
ip netns add A
|
|
ip netns add B
|
|
ip link add veth0 type veth peer name veth1
|
|
ip link set veth0 netns A
|
|
ip link set veth1 netns B
|
|
|
|
ip netns exec A ip link set lo up
|
|
ip netns exec A ip link set veth0 up
|
|
ip netns exec A ip -6 a a 2001:db8:0::1/64 dev veth0
|
|
ip netns exec B ip link set lo up
|
|
ip netns exec B ip link set veth1 up
|
|
ip netns exec B ip -6 a a 2001:db8:0::2/64 dev veth1
|
|
for i in {1..99}
|
|
do
|
|
let A=$i-1
|
|
ip netns exec A ip link add ip6gre$i type ip6gre \
|
|
local 2001:db8:$A::1 remote 2001:db8:$A::2 encaplimit 100
|
|
ip netns exec A ip -6 a a 2001:db8:$i::1/64 dev ip6gre$i
|
|
ip netns exec A ip link set ip6gre$i up
|
|
|
|
ip netns exec B ip link add ip6gre$i type ip6gre \
|
|
local 2001:db8:$A::2 remote 2001:db8:$A::1 encaplimit 100
|
|
ip netns exec B ip -6 a a 2001:db8:$i::2/64 dev ip6gre$i
|
|
ip netns exec B ip link set ip6gre$i up
|
|
done
|
|
|
|
Splat looks like:
|
|
kernel BUG at net/core/skbuff.c:110!
|
|
invalid opcode: 0000 [#1] SMP DEBUG_PAGEALLOC KASAN PTI
|
|
CPU: 0 PID: 7 Comm: kworker/0:1 Not tainted 5.12.0+ #891
|
|
Workqueue: ipv6_addrconf addrconf_dad_work
|
|
RIP: 0010:skb_panic+0x15d/0x15f
|
|
Code: 92 fe 4c 8b 4c 24 10 53 8b 4d 70 45 89 e0 48 c7 c7 00 ae 79 83
|
|
41 57 41 56 41 55 48 8b 54 24 a6 26 f9 ff <0f> 0b 48 8b 6c 24 20 89
|
|
34 24 e8 4a 4e 92 fe 8b 34 24 48 c7 c1 20
|
|
RSP: 0018:ffff88810091f820 EFLAGS: 00010282
|
|
RAX: 0000000000000089 RBX: ffff8881086e9000 RCX: 0000000000000000
|
|
RDX: 0000000000000089 RSI: 0000000000000008 RDI: ffffed1020123efb
|
|
RBP: ffff888005f6eac0 R08: ffffed1022fc0031 R09: ffffed1022fc0031
|
|
R10: ffff888117e00187 R11: ffffed1022fc0030 R12: 0000000000000028
|
|
R13: ffff888008284eb0 R14: 0000000000000ed8 R15: 0000000000000ec0
|
|
FS: 0000000000000000(0000) GS:ffff888117c00000(0000)
|
|
knlGS:0000000000000000
|
|
CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
|
|
CR2: 00007f8b801c5640 CR3: 0000000033c2c006 CR4: 00000000003706f0
|
|
DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000
|
|
DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400
|
|
Call Trace:
|
|
? ip6_mc_hdr.isra.26.constprop.46+0x12a/0x600
|
|
? ip6_mc_hdr.isra.26.constprop.46+0x12a/0x600
|
|
skb_put.cold.104+0x22/0x22
|
|
ip6_mc_hdr.isra.26.constprop.46+0x12a/0x600
|
|
? rcu_read_lock_sched_held+0x91/0xc0
|
|
mld_newpack+0x398/0x8f0
|
|
? ip6_mc_hdr.isra.26.constprop.46+0x600/0x600
|
|
? lock_contended+0xc40/0xc40
|
|
add_grhead.isra.33+0x280/0x380
|
|
add_grec+0x5ca/0xff0
|
|
? mld_sendpack+0xf40/0xf40
|
|
? lock_downgrade+0x690/0x690
|
|
mld_send_initial_cr.part.34+0xb9/0x180
|
|
ipv6_mc_dad_complete+0x15d/0x1b0
|
|
addrconf_dad_completed+0x8d2/0xbb0
|
|
? lock_downgrade+0x690/0x690
|
|
? addrconf_rs_timer+0x660/0x660
|
|
? addrconf_dad_work+0x73c/0x10e0
|
|
addrconf_dad_work+0x73c/0x10e0
|
|
|
|
Allowing high order page allocation could fix this problem.</Note>
|
|
</Notes>
|
|
<ReleaseDate>2024-04-19</ReleaseDate>
|
|
<CVE>CVE-2021-47146</CVE>
|
|
<ProductStatuses>
|
|
<Status Type="Fixed">
|
|
<ProductID>openEuler-20.03-LTS-SP4</ProductID>
|
|
</Status>
|
|
</ProductStatuses>
|
|
<Threats>
|
|
<Threat Type="Impact">
|
|
<Description>Medium</Description>
|
|
</Threat>
|
|
</Threats>
|
|
<CVSSScoreSets>
|
|
<ScoreSet>
|
|
<BaseScore>5.5</BaseScore>
|
|
<Vector>AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H</Vector>
|
|
</ScoreSet>
|
|
</CVSSScoreSets>
|
|
<Remediations>
|
|
<Remediation Type="Vendor Fix">
|
|
<Description>kernel security update</Description>
|
|
<DATE>2024-04-19</DATE>
|
|
<URL>https://www.openeuler.org/en/security/safety-bulletin/detail.html?id=openEuler-SA-2024-1484</URL>
|
|
</Remediation>
|
|
</Remediations>
|
|
</Vulnerability>
|
|
<Vulnerability Ordinal="19" xmlns="http://www.icasi.org/CVRF/schema/vuln/1.1">
|
|
<Notes>
|
|
<Note Title="Vulnerability Description" Type="General" Ordinal="19" xml:lang="en">In the Linux kernel, the following vulnerability has been resolved:
|
|
|
|
i2c: i801: Don't generate an interrupt on bus reset
|
|
|
|
Now that the i2c-i801 driver supports interrupts, setting the KILL bit
|
|
in a attempt to recover from a timed out transaction triggers an
|
|
interrupt. Unfortunately, the interrupt handler (i801_isr) is not
|
|
prepared for this situation and will try to process the interrupt as
|
|
if it was signaling the end of a successful transaction. In the case
|
|
of a block transaction, this can result in an out-of-range memory
|
|
access.
|
|
|
|
This condition was reproduced several times by syzbot:
|
|
https://syzkaller.appspot.com/bug?extid=ed71512d469895b5b34e
|
|
https://syzkaller.appspot.com/bug?extid=8c8dedc0ba9e03f6c79e
|
|
https://syzkaller.appspot.com/bug?extid=c8ff0b6d6c73d81b610e
|
|
https://syzkaller.appspot.com/bug?extid=33f6c360821c399d69eb
|
|
https://syzkaller.appspot.com/bug?extid=be15dc0b1933f04b043a
|
|
https://syzkaller.appspot.com/bug?extid=b4d3fd1dfd53e90afd79
|
|
|
|
So disable interrupts while trying to reset the bus. Interrupts will
|
|
be enabled again for the following transaction.</Note>
|
|
</Notes>
|
|
<ReleaseDate>2024-04-19</ReleaseDate>
|
|
<CVE>CVE-2021-47153</CVE>
|
|
<ProductStatuses>
|
|
<Status Type="Fixed">
|
|
<ProductID>openEuler-20.03-LTS-SP4</ProductID>
|
|
</Status>
|
|
</ProductStatuses>
|
|
<Threats>
|
|
<Threat Type="Impact">
|
|
<Description>Medium</Description>
|
|
</Threat>
|
|
</Threats>
|
|
<CVSSScoreSets>
|
|
<ScoreSet>
|
|
<BaseScore>5.5</BaseScore>
|
|
<Vector>AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H</Vector>
|
|
</ScoreSet>
|
|
</CVSSScoreSets>
|
|
<Remediations>
|
|
<Remediation Type="Vendor Fix">
|
|
<Description>kernel security update</Description>
|
|
<DATE>2024-04-19</DATE>
|
|
<URL>https://www.openeuler.org/en/security/safety-bulletin/detail.html?id=openEuler-SA-2024-1484</URL>
|
|
</Remediation>
|
|
</Remediations>
|
|
</Vulnerability>
|
|
<Vulnerability Ordinal="20" xmlns="http://www.icasi.org/CVRF/schema/vuln/1.1">
|
|
<Notes>
|
|
<Note Title="Vulnerability Description" Type="General" Ordinal="20" xml:lang="en">In the Linux kernel, the following vulnerability has been resolved:
|
|
|
|
net: dsa: fix a crash if ->get_sset_count() fails
|
|
|
|
If ds->ops->get_sset_count() fails then it "count" is a negative error
|
|
code such as -EOPNOTSUPP. Because "i" is an unsigned int, the negative
|
|
error code is type promoted to a very high value and the loop will
|
|
corrupt memory until the system crashes.
|
|
|
|
Fix this by checking for error codes and changing the type of "i" to
|
|
just int.</Note>
|
|
</Notes>
|
|
<ReleaseDate>2024-04-19</ReleaseDate>
|
|
<CVE>CVE-2021-47159</CVE>
|
|
<ProductStatuses>
|
|
<Status Type="Fixed">
|
|
<ProductID>openEuler-20.03-LTS-SP4</ProductID>
|
|
</Status>
|
|
</ProductStatuses>
|
|
<Threats>
|
|
<Threat Type="Impact">
|
|
<Description>Medium</Description>
|
|
</Threat>
|
|
</Threats>
|
|
<CVSSScoreSets>
|
|
<ScoreSet>
|
|
<BaseScore>5.5</BaseScore>
|
|
<Vector>AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H</Vector>
|
|
</ScoreSet>
|
|
</CVSSScoreSets>
|
|
<Remediations>
|
|
<Remediation Type="Vendor Fix">
|
|
<Description>kernel security update</Description>
|
|
<DATE>2024-04-19</DATE>
|
|
<URL>https://www.openeuler.org/en/security/safety-bulletin/detail.html?id=openEuler-SA-2024-1484</URL>
|
|
</Remediation>
|
|
</Remediations>
|
|
</Vulnerability>
|
|
<Vulnerability Ordinal="21" xmlns="http://www.icasi.org/CVRF/schema/vuln/1.1">
|
|
<Notes>
|
|
<Note Title="Vulnerability Description" Type="General" Ordinal="21" xml:lang="en">In the Linux kernel, the following vulnerability has been resolved:
|
|
|
|
net: dsa: mt7530: fix VLAN traffic leaks
|
|
|
|
PCR_MATRIX field was set to all 1's when VLAN filtering is enabled, but
|
|
was not reset when it is disabled, which may cause traffic leaks:
|
|
|
|
ip link add br0 type bridge vlan_filtering 1
|
|
ip link add br1 type bridge vlan_filtering 1
|
|
ip link set swp0 master br0
|
|
ip link set swp1 master br1
|
|
ip link set br0 type bridge vlan_filtering 0
|
|
ip link set br1 type bridge vlan_filtering 0
|
|
# traffic in br0 and br1 will start leaking to each other
|
|
|
|
As port_bridge_{add,del} have set up PCR_MATRIX properly, remove the
|
|
PCR_MATRIX write from mt7530_port_set_vlan_aware.</Note>
|
|
</Notes>
|
|
<ReleaseDate>2024-04-19</ReleaseDate>
|
|
<CVE>CVE-2021-47160</CVE>
|
|
<ProductStatuses>
|
|
<Status Type="Fixed">
|
|
<ProductID>openEuler-20.03-LTS-SP4</ProductID>
|
|
</Status>
|
|
</ProductStatuses>
|
|
<Threats>
|
|
<Threat Type="Impact">
|
|
<Description>Medium</Description>
|
|
</Threat>
|
|
</Threats>
|
|
<CVSSScoreSets>
|
|
<ScoreSet>
|
|
<BaseScore>5.5</BaseScore>
|
|
<Vector>AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H</Vector>
|
|
</ScoreSet>
|
|
</CVSSScoreSets>
|
|
<Remediations>
|
|
<Remediation Type="Vendor Fix">
|
|
<Description>kernel security update</Description>
|
|
<DATE>2024-04-19</DATE>
|
|
<URL>https://www.openeuler.org/en/security/safety-bulletin/detail.html?id=openEuler-SA-2024-1484</URL>
|
|
</Remediation>
|
|
</Remediations>
|
|
</Vulnerability>
|
|
<Vulnerability Ordinal="22" xmlns="http://www.icasi.org/CVRF/schema/vuln/1.1">
|
|
<Notes>
|
|
<Note Title="Vulnerability Description" Type="General" Ordinal="22" xml:lang="en">In the Linux kernel, the following vulnerability has been resolved:
|
|
|
|
spi: spi-fsl-dspi: Fix a resource leak in an error handling path
|
|
|
|
'dspi_request_dma()' should be undone by a 'dspi_release_dma()' call in the
|
|
error handling path of the probe function, as already done in the remove
|
|
function</Note>
|
|
</Notes>
|
|
<ReleaseDate>2024-04-19</ReleaseDate>
|
|
<CVE>CVE-2021-47161</CVE>
|
|
<ProductStatuses>
|
|
<Status Type="Fixed">
|
|
<ProductID>openEuler-20.03-LTS-SP4</ProductID>
|
|
</Status>
|
|
</ProductStatuses>
|
|
<Threats>
|
|
<Threat Type="Impact">
|
|
<Description>Medium</Description>
|
|
</Threat>
|
|
</Threats>
|
|
<CVSSScoreSets>
|
|
<ScoreSet>
|
|
<BaseScore>5.5</BaseScore>
|
|
<Vector>AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H</Vector>
|
|
</ScoreSet>
|
|
</CVSSScoreSets>
|
|
<Remediations>
|
|
<Remediation Type="Vendor Fix">
|
|
<Description>kernel security update</Description>
|
|
<DATE>2024-04-19</DATE>
|
|
<URL>https://www.openeuler.org/en/security/safety-bulletin/detail.html?id=openEuler-SA-2024-1484</URL>
|
|
</Remediation>
|
|
</Remediations>
|
|
</Vulnerability>
|
|
<Vulnerability Ordinal="23" xmlns="http://www.icasi.org/CVRF/schema/vuln/1.1">
|
|
<Notes>
|
|
<Note Title="Vulnerability Description" Type="General" Ordinal="23" xml:lang="en">In the Linux kernel, the following vulnerability has been resolved:
|
|
|
|
tipc: skb_linearize the head skb when reassembling msgs
|
|
|
|
It's not a good idea to append the frag skb to a skb's frag_list if
|
|
the frag_list already has skbs from elsewhere, such as this skb was
|
|
created by pskb_copy() where the frag_list was cloned (all the skbs
|
|
in it were skb_get'ed) and shared by multiple skbs.
|
|
|
|
However, the new appended frag skb should have been only seen by the
|
|
current skb. Otherwise, it will cause use after free crashes as this
|
|
appended frag skb are seen by multiple skbs but it only got skb_get
|
|
called once.
|
|
|
|
The same thing happens with a skb updated by pskb_may_pull() with a
|
|
skb_cloned skb. Li Shuang has reported quite a few crashes caused
|
|
by this when doing testing over macvlan devices:
|
|
|
|
[] kernel BUG at net/core/skbuff.c:1970!
|
|
[] Call Trace:
|
|
[] skb_clone+0x4d/0xb0
|
|
[] macvlan_broadcast+0xd8/0x160 [macvlan]
|
|
[] macvlan_process_broadcast+0x148/0x150 [macvlan]
|
|
[] process_one_work+0x1a7/0x360
|
|
[] worker_thread+0x30/0x390
|
|
|
|
[] kernel BUG at mm/usercopy.c:102!
|
|
[] Call Trace:
|
|
[] __check_heap_object+0xd3/0x100
|
|
[] __check_object_size+0xff/0x16b
|
|
[] simple_copy_to_iter+0x1c/0x30
|
|
[] __skb_datagram_iter+0x7d/0x310
|
|
[] __skb_datagram_iter+0x2a5/0x310
|
|
[] skb_copy_datagram_iter+0x3b/0x90
|
|
[] tipc_recvmsg+0x14a/0x3a0 [tipc]
|
|
[] ____sys_recvmsg+0x91/0x150
|
|
[] ___sys_recvmsg+0x7b/0xc0
|
|
|
|
[] kernel BUG at mm/slub.c:305!
|
|
[] Call Trace:
|
|
[] <IRQ>
|
|
[] kmem_cache_free+0x3ff/0x400
|
|
[] __netif_receive_skb_core+0x12c/0xc40
|
|
[] ? kmem_cache_alloc+0x12e/0x270
|
|
[] netif_receive_skb_internal+0x3d/0xb0
|
|
[] ? get_rx_page_info+0x8e/0xa0 [be2net]
|
|
[] be_poll+0x6ef/0xd00 [be2net]
|
|
[] ? irq_exit+0x4f/0x100
|
|
[] net_rx_action+0x149/0x3b0
|
|
|
|
...
|
|
|
|
This patch is to fix it by linearizing the head skb if it has frag_list
|
|
set in tipc_buf_append(). Note that we choose to do this before calling
|
|
skb_unshare(), as __skb_linearize() will avoid skb_copy(). Also, we can
|
|
not just drop the frag_list either as the early time.</Note>
|
|
</Notes>
|
|
<ReleaseDate>2024-04-19</ReleaseDate>
|
|
<CVE>CVE-2021-47162</CVE>
|
|
<ProductStatuses>
|
|
<Status Type="Fixed">
|
|
<ProductID>openEuler-20.03-LTS-SP4</ProductID>
|
|
</Status>
|
|
</ProductStatuses>
|
|
<Threats>
|
|
<Threat Type="Impact">
|
|
<Description>Medium</Description>
|
|
</Threat>
|
|
</Threats>
|
|
<CVSSScoreSets>
|
|
<ScoreSet>
|
|
<BaseScore>5.5</BaseScore>
|
|
<Vector>AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H</Vector>
|
|
</ScoreSet>
|
|
</CVSSScoreSets>
|
|
<Remediations>
|
|
<Remediation Type="Vendor Fix">
|
|
<Description>kernel security update</Description>
|
|
<DATE>2024-04-19</DATE>
|
|
<URL>https://www.openeuler.org/en/security/safety-bulletin/detail.html?id=openEuler-SA-2024-1484</URL>
|
|
</Remediation>
|
|
</Remediations>
|
|
</Vulnerability>
|
|
<Vulnerability Ordinal="24" xmlns="http://www.icasi.org/CVRF/schema/vuln/1.1">
|
|
<Notes>
|
|
<Note Title="Vulnerability Description" Type="General" Ordinal="24" xml:lang="en">In the Linux kernel, the following vulnerability has been resolved:
|
|
|
|
tipc: wait and exit until all work queues are done
|
|
|
|
On some host, a crash could be triggered simply by repeating these
|
|
commands several times:
|
|
|
|
# modprobe tipc
|
|
# tipc bearer enable media udp name UDP1 localip 127.0.0.1
|
|
# rmmod tipc
|
|
|
|
[] BUG: unable to handle kernel paging request at ffffffffc096bb00
|
|
[] Workqueue: events 0xffffffffc096bb00
|
|
[] Call Trace:
|
|
[] ? process_one_work+0x1a7/0x360
|
|
[] ? worker_thread+0x30/0x390
|
|
[] ? create_worker+0x1a0/0x1a0
|
|
[] ? kthread+0x116/0x130
|
|
[] ? kthread_flush_work_fn+0x10/0x10
|
|
[] ? ret_from_fork+0x35/0x40
|
|
|
|
When removing the TIPC module, the UDP tunnel sock will be delayed to
|
|
release in a work queue as sock_release() can't be done in rtnl_lock().
|
|
If the work queue is schedule to run after the TIPC module is removed,
|
|
kernel will crash as the work queue function cleanup_beareri() code no
|
|
longer exists when trying to invoke it.
|
|
|
|
To fix it, this patch introduce a member wq_count in tipc_net to track
|
|
the numbers of work queues in schedule, and wait and exit until all
|
|
work queues are done in tipc_exit_net().</Note>
|
|
</Notes>
|
|
<ReleaseDate>2024-04-19</ReleaseDate>
|
|
<CVE>CVE-2021-47163</CVE>
|
|
<ProductStatuses>
|
|
<Status Type="Fixed">
|
|
<ProductID>openEuler-20.03-LTS-SP4</ProductID>
|
|
</Status>
|
|
</ProductStatuses>
|
|
<Threats>
|
|
<Threat Type="Impact">
|
|
<Description>Medium</Description>
|
|
</Threat>
|
|
</Threats>
|
|
<CVSSScoreSets>
|
|
<ScoreSet>
|
|
<BaseScore>5.5</BaseScore>
|
|
<Vector>AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H</Vector>
|
|
</ScoreSet>
|
|
</CVSSScoreSets>
|
|
<Remediations>
|
|
<Remediation Type="Vendor Fix">
|
|
<Description>kernel security update</Description>
|
|
<DATE>2024-04-19</DATE>
|
|
<URL>https://www.openeuler.org/en/security/safety-bulletin/detail.html?id=openEuler-SA-2024-1484</URL>
|
|
</Remediation>
|
|
</Remediations>
|
|
</Vulnerability>
|
|
<Vulnerability Ordinal="25" xmlns="http://www.icasi.org/CVRF/schema/vuln/1.1">
|
|
<Notes>
|
|
<Note Title="Vulnerability Description" Type="General" Ordinal="25" xml:lang="en">In the Linux kernel, the following vulnerability has been resolved:
|
|
|
|
NFS: Fix an Oopsable condition in __nfs_pageio_add_request()
|
|
|
|
Ensure that nfs_pageio_error_cleanup() resets the mirror array contents,
|
|
so that the structure reflects the fact that it is now empty.
|
|
Also change the test in nfs_pageio_do_add_request() to be more robust by
|
|
checking whether or not the list is empty rather than relying on the
|
|
value of pg_count.</Note>
|
|
</Notes>
|
|
<ReleaseDate>2024-04-19</ReleaseDate>
|
|
<CVE>CVE-2021-47167</CVE>
|
|
<ProductStatuses>
|
|
<Status Type="Fixed">
|
|
<ProductID>openEuler-20.03-LTS-SP4</ProductID>
|
|
</Status>
|
|
</ProductStatuses>
|
|
<Threats>
|
|
<Threat Type="Impact">
|
|
<Description>Medium</Description>
|
|
</Threat>
|
|
</Threats>
|
|
<CVSSScoreSets>
|
|
<ScoreSet>
|
|
<BaseScore>5.5</BaseScore>
|
|
<Vector>AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H</Vector>
|
|
</ScoreSet>
|
|
</CVSSScoreSets>
|
|
<Remediations>
|
|
<Remediation Type="Vendor Fix">
|
|
<Description>kernel security update</Description>
|
|
<DATE>2024-04-19</DATE>
|
|
<URL>https://www.openeuler.org/en/security/safety-bulletin/detail.html?id=openEuler-SA-2024-1484</URL>
|
|
</Remediation>
|
|
</Remediations>
|
|
</Vulnerability>
|
|
<Vulnerability Ordinal="26" xmlns="http://www.icasi.org/CVRF/schema/vuln/1.1">
|
|
<Notes>
|
|
<Note Title="Vulnerability Description" Type="General" Ordinal="26" xml:lang="en">In the Linux kernel, the following vulnerability has been resolved:
|
|
|
|
USB: usbfs: Don't WARN about excessively large memory allocations
|
|
|
|
Syzbot found that the kernel generates a WARNing if the user tries to
|
|
submit a bulk transfer through usbfs with a buffer that is way too
|
|
large. This isn't a bug in the kernel; it's merely an invalid request
|
|
from the user and the usbfs code does handle it correctly.
|
|
|
|
In theory the same thing can happen with async transfers, or with the
|
|
packet descriptor table for isochronous transfers.
|
|
|
|
To prevent the MM subsystem from complaining about these bad
|
|
allocation requests, add the __GFP_NOWARN flag to the kmalloc calls
|
|
for these buffers.</Note>
|
|
</Notes>
|
|
<ReleaseDate>2024-04-19</ReleaseDate>
|
|
<CVE>CVE-2021-47170</CVE>
|
|
<ProductStatuses>
|
|
<Status Type="Fixed">
|
|
<ProductID>openEuler-20.03-LTS-SP4</ProductID>
|
|
</Status>
|
|
</ProductStatuses>
|
|
<Threats>
|
|
<Threat Type="Impact">
|
|
<Description>Medium</Description>
|
|
</Threat>
|
|
</Threats>
|
|
<CVSSScoreSets>
|
|
<ScoreSet>
|
|
<BaseScore>5.5</BaseScore>
|
|
<Vector>AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H</Vector>
|
|
</ScoreSet>
|
|
</CVSSScoreSets>
|
|
<Remediations>
|
|
<Remediation Type="Vendor Fix">
|
|
<Description>kernel security update</Description>
|
|
<DATE>2024-04-19</DATE>
|
|
<URL>https://www.openeuler.org/en/security/safety-bulletin/detail.html?id=openEuler-SA-2024-1484</URL>
|
|
</Remediation>
|
|
</Remediations>
|
|
</Vulnerability>
|
|
<Vulnerability Ordinal="27" xmlns="http://www.icasi.org/CVRF/schema/vuln/1.1">
|
|
<Notes>
|
|
<Note Title="Vulnerability Description" Type="General" Ordinal="27" xml:lang="en">In the Linux kernel, the following vulnerability has been resolved:
|
|
|
|
net: usb: fix memory leak in smsc75xx_bind
|
|
|
|
Syzbot reported memory leak in smsc75xx_bind().
|
|
The problem was is non-freed memory in case of
|
|
errors after memory allocation.
|
|
|
|
backtrace:
|
|
[<ffffffff84245b62>] kmalloc include/linux/slab.h:556 [inline]
|
|
[<ffffffff84245b62>] kzalloc include/linux/slab.h:686 [inline]
|
|
[<ffffffff84245b62>] smsc75xx_bind+0x7a/0x334 drivers/net/usb/smsc75xx.c:1460
|
|
[<ffffffff82b5b2e6>] usbnet_probe+0x3b6/0xc30 drivers/net/usb/usbnet.c:1728</Note>
|
|
</Notes>
|
|
<ReleaseDate>2024-04-19</ReleaseDate>
|
|
<CVE>CVE-2021-47171</CVE>
|
|
<ProductStatuses>
|
|
<Status Type="Fixed">
|
|
<ProductID>openEuler-20.03-LTS-SP4</ProductID>
|
|
</Status>
|
|
</ProductStatuses>
|
|
<Threats>
|
|
<Threat Type="Impact">
|
|
<Description>Medium</Description>
|
|
</Threat>
|
|
</Threats>
|
|
<CVSSScoreSets>
|
|
<ScoreSet>
|
|
<BaseScore>5.5</BaseScore>
|
|
<Vector>AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H</Vector>
|
|
</ScoreSet>
|
|
</CVSSScoreSets>
|
|
<Remediations>
|
|
<Remediation Type="Vendor Fix">
|
|
<Description>kernel security update</Description>
|
|
<DATE>2024-04-19</DATE>
|
|
<URL>https://www.openeuler.org/en/security/safety-bulletin/detail.html?id=openEuler-SA-2024-1484</URL>
|
|
</Remediation>
|
|
</Remediations>
|
|
</Vulnerability>
|
|
<Vulnerability Ordinal="28" xmlns="http://www.icasi.org/CVRF/schema/vuln/1.1">
|
|
<Notes>
|
|
<Note Title="Vulnerability Description" Type="General" Ordinal="28" xml:lang="en">In the Linux kernel, the following vulnerability has been resolved:
|
|
|
|
misc/uss720: fix memory leak in uss720_probe
|
|
|
|
uss720_probe forgets to decrease the refcount of usbdev in uss720_probe.
|
|
Fix this by decreasing the refcount of usbdev by usb_put_dev.
|
|
|
|
BUG: memory leak
|
|
unreferenced object 0xffff888101113800 (size 2048):
|
|
comm "kworker/0:1", pid 7, jiffies 4294956777 (age 28.870s)
|
|
hex dump (first 32 bytes):
|
|
ff ff ff ff 31 00 00 00 00 00 00 00 00 00 00 00 ....1...........
|
|
00 00 00 00 00 00 00 00 00 00 00 00 03 00 00 00 ................
|
|
backtrace:
|
|
[<ffffffff82b8e822>] kmalloc include/linux/slab.h:554 [inline]
|
|
[<ffffffff82b8e822>] kzalloc include/linux/slab.h:684 [inline]
|
|
[<ffffffff82b8e822>] usb_alloc_dev+0x32/0x450 drivers/usb/core/usb.c:582
|
|
[<ffffffff82b98441>] hub_port_connect drivers/usb/core/hub.c:5129 [inline]
|
|
[<ffffffff82b98441>] hub_port_connect_change drivers/usb/core/hub.c:5363 [inline]
|
|
[<ffffffff82b98441>] port_event drivers/usb/core/hub.c:5509 [inline]
|
|
[<ffffffff82b98441>] hub_event+0x1171/0x20c0 drivers/usb/core/hub.c:5591
|
|
[<ffffffff81259229>] process_one_work+0x2c9/0x600 kernel/workqueue.c:2275
|
|
[<ffffffff81259b19>] worker_thread+0x59/0x5d0 kernel/workqueue.c:2421
|
|
[<ffffffff81261228>] kthread+0x178/0x1b0 kernel/kthread.c:292
|
|
[<ffffffff8100227f>] ret_from_fork+0x1f/0x30 arch/x86/entry/entry_64.S:294</Note>
|
|
</Notes>
|
|
<ReleaseDate>2024-04-19</ReleaseDate>
|
|
<CVE>CVE-2021-47173</CVE>
|
|
<ProductStatuses>
|
|
<Status Type="Fixed">
|
|
<ProductID>openEuler-20.03-LTS-SP4</ProductID>
|
|
</Status>
|
|
</ProductStatuses>
|
|
<Threats>
|
|
<Threat Type="Impact">
|
|
<Description>Medium</Description>
|
|
</Threat>
|
|
</Threats>
|
|
<CVSSScoreSets>
|
|
<ScoreSet>
|
|
<BaseScore>5.5</BaseScore>
|
|
<Vector>AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H</Vector>
|
|
</ScoreSet>
|
|
</CVSSScoreSets>
|
|
<Remediations>
|
|
<Remediation Type="Vendor Fix">
|
|
<Description>kernel security update</Description>
|
|
<DATE>2024-04-19</DATE>
|
|
<URL>https://www.openeuler.org/en/security/safety-bulletin/detail.html?id=openEuler-SA-2024-1484</URL>
|
|
</Remediation>
|
|
</Remediations>
|
|
</Vulnerability>
|
|
<Vulnerability Ordinal="29" xmlns="http://www.icasi.org/CVRF/schema/vuln/1.1">
|
|
<Notes>
|
|
<Note Title="Vulnerability Description" Type="General" Ordinal="29" xml:lang="en">In the Linux kernel, the following vulnerability has been resolved:
|
|
|
|
NFC: nci: fix memory leak in nci_allocate_device
|
|
|
|
nfcmrvl_disconnect fails to free the hci_dev field in struct nci_dev.
|
|
Fix this by freeing hci_dev in nci_free_device.
|
|
|
|
BUG: memory leak
|
|
unreferenced object 0xffff888111ea6800 (size 1024):
|
|
comm "kworker/1:0", pid 19, jiffies 4294942308 (age 13.580s)
|
|
hex dump (first 32 bytes):
|
|
00 00 00 00 00 00 00 00 00 60 fd 0c 81 88 ff ff .........`......
|
|
00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................
|
|
backtrace:
|
|
[<000000004bc25d43>] kmalloc include/linux/slab.h:552 [inline]
|
|
[<000000004bc25d43>] kzalloc include/linux/slab.h:682 [inline]
|
|
[<000000004bc25d43>] nci_hci_allocate+0x21/0xd0 net/nfc/nci/hci.c:784
|
|
[<00000000c59cff92>] nci_allocate_device net/nfc/nci/core.c:1170 [inline]
|
|
[<00000000c59cff92>] nci_allocate_device+0x10b/0x160 net/nfc/nci/core.c:1132
|
|
[<00000000006e0a8e>] nfcmrvl_nci_register_dev+0x10a/0x1c0 drivers/nfc/nfcmrvl/main.c:153
|
|
[<000000004da1b57e>] nfcmrvl_probe+0x223/0x290 drivers/nfc/nfcmrvl/usb.c:345
|
|
[<00000000d506aed9>] usb_probe_interface+0x177/0x370 drivers/usb/core/driver.c:396
|
|
[<00000000bc632c92>] really_probe+0x159/0x4a0 drivers/base/dd.c:554
|
|
[<00000000f5009125>] driver_probe_device+0x84/0x100 drivers/base/dd.c:740
|
|
[<000000000ce658ca>] __device_attach_driver+0xee/0x110 drivers/base/dd.c:846
|
|
[<000000007067d05f>] bus_for_each_drv+0xb7/0x100 drivers/base/bus.c:431
|
|
[<00000000f8e13372>] __device_attach+0x122/0x250 drivers/base/dd.c:914
|
|
[<000000009cf68860>] bus_probe_device+0xc6/0xe0 drivers/base/bus.c:491
|
|
[<00000000359c965a>] device_add+0x5be/0xc30 drivers/base/core.c:3109
|
|
[<00000000086e4bd3>] usb_set_configuration+0x9d9/0xb90 drivers/usb/core/message.c:2164
|
|
[<00000000ca036872>] usb_generic_driver_probe+0x8c/0xc0 drivers/usb/core/generic.c:238
|
|
[<00000000d40d36f6>] usb_probe_device+0x5c/0x140 drivers/usb/core/driver.c:293
|
|
[<00000000bc632c92>] really_probe+0x159/0x4a0 drivers/base/dd.c:554</Note>
|
|
</Notes>
|
|
<ReleaseDate>2024-04-19</ReleaseDate>
|
|
<CVE>CVE-2021-47180</CVE>
|
|
<ProductStatuses>
|
|
<Status Type="Fixed">
|
|
<ProductID>openEuler-20.03-LTS-SP4</ProductID>
|
|
</Status>
|
|
</ProductStatuses>
|
|
<Threats>
|
|
<Threat Type="Impact">
|
|
<Description>Medium</Description>
|
|
</Threat>
|
|
</Threats>
|
|
<CVSSScoreSets>
|
|
<ScoreSet>
|
|
<BaseScore>5.5</BaseScore>
|
|
<Vector>AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H</Vector>
|
|
</ScoreSet>
|
|
</CVSSScoreSets>
|
|
<Remediations>
|
|
<Remediation Type="Vendor Fix">
|
|
<Description>kernel security update</Description>
|
|
<DATE>2024-04-19</DATE>
|
|
<URL>https://www.openeuler.org/en/security/safety-bulletin/detail.html?id=openEuler-SA-2024-1484</URL>
|
|
</Remediation>
|
|
</Remediations>
|
|
</Vulnerability>
|
|
<Vulnerability Ordinal="30" xmlns="http://www.icasi.org/CVRF/schema/vuln/1.1">
|
|
<Notes>
|
|
<Note Title="Vulnerability Description" Type="General" Ordinal="30" xml:lang="en">In the Linux kernel, the following vulnerability has been resolved:EDAC/thunderx: Fix possible out-of-bounds string accessEnabling -Wstringop-overflow globally exposes a warning for a common bugin the usage of strncat(): drivers/edac/thunderx_edac.c: In function thunderx_ocx_com_threaded_isr : drivers/edac/thunderx_edac.c:1136:17: error: strncat specified bound 1024 equals destination size [-Werror=stringop-overflow=] 1136 | strncat(msg, other, OCX_MESSAGE_SIZE); | ^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ ... 1145 | strncat(msg, other, OCX_MESSAGE_SIZE); ... 1150 | strncat(msg, other, OCX_MESSAGE_SIZE); ...Apparently the author of this driver expected strncat() to behave theway that strlcat() does, which uses the size of the destination bufferas its third argument rather than the length of the source buffer. Theresult is that there is no check on the size of the allocated buffer.Change it to strlcat(). [ bp: Trim compiler output, fixup commit message. ]</Note>
|
|
</Notes>
|
|
<ReleaseDate>2024-04-19</ReleaseDate>
|
|
<CVE>CVE-2023-52464</CVE>
|
|
<ProductStatuses>
|
|
<Status Type="Fixed">
|
|
<ProductID>openEuler-20.03-LTS-SP4</ProductID>
|
|
</Status>
|
|
</ProductStatuses>
|
|
<Threats>
|
|
<Threat Type="Impact">
|
|
<Description>Medium</Description>
|
|
</Threat>
|
|
</Threats>
|
|
<CVSSScoreSets>
|
|
<ScoreSet>
|
|
<BaseScore>5.5</BaseScore>
|
|
<Vector>AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N</Vector>
|
|
</ScoreSet>
|
|
</CVSSScoreSets>
|
|
<Remediations>
|
|
<Remediation Type="Vendor Fix">
|
|
<Description>kernel security update</Description>
|
|
<DATE>2024-04-19</DATE>
|
|
<URL>https://www.openeuler.org/en/security/safety-bulletin/detail.html?id=openEuler-SA-2024-1484</URL>
|
|
</Remediation>
|
|
</Remediations>
|
|
</Vulnerability>
|
|
<Vulnerability Ordinal="31" xmlns="http://www.icasi.org/CVRF/schema/vuln/1.1">
|
|
<Notes>
|
|
<Note Title="Vulnerability Description" Type="General" Ordinal="31" xml:lang="en">In the Linux kernel, the following vulnerability has been resolved:
|
|
|
|
Input: powermate - fix use-after-free in powermate_config_complete
|
|
|
|
syzbot has found a use-after-free bug [1] in the powermate driver. This
|
|
happens when the device is disconnected, which leads to a memory free from
|
|
the powermate_device struct. When an asynchronous control message
|
|
completes after the kfree and its callback is invoked, the lock does not
|
|
exist anymore and hence the bug.
|
|
|
|
Use usb_kill_urb() on pm->config to cancel any in-progress requests upon
|
|
device disconnection.
|
|
|
|
[1] https://syzkaller.appspot.com/bug?extid=0434ac83f907a1dbdd1e</Note>
|
|
</Notes>
|
|
<ReleaseDate>2024-04-19</ReleaseDate>
|
|
<CVE>CVE-2023-52475</CVE>
|
|
<ProductStatuses>
|
|
<Status Type="Fixed">
|
|
<ProductID>openEuler-20.03-LTS-SP4</ProductID>
|
|
</Status>
|
|
</ProductStatuses>
|
|
<Threats>
|
|
<Threat Type="Impact">
|
|
<Description>Medium</Description>
|
|
</Threat>
|
|
</Threats>
|
|
<CVSSScoreSets>
|
|
<ScoreSet>
|
|
<BaseScore>6.3</BaseScore>
|
|
<Vector>AV:P/AC:H/PR:L/UI:N/S:U/C:H/I:H/A:H</Vector>
|
|
</ScoreSet>
|
|
</CVSSScoreSets>
|
|
<Remediations>
|
|
<Remediation Type="Vendor Fix">
|
|
<Description>kernel security update</Description>
|
|
<DATE>2024-04-19</DATE>
|
|
<URL>https://www.openeuler.org/en/security/safety-bulletin/detail.html?id=openEuler-SA-2024-1484</URL>
|
|
</Remediation>
|
|
</Remediations>
|
|
</Vulnerability>
|
|
<Vulnerability Ordinal="32" xmlns="http://www.icasi.org/CVRF/schema/vuln/1.1">
|
|
<Notes>
|
|
<Note Title="Vulnerability Description" Type="General" Ordinal="32" xml:lang="en">In the Linux kernel, the following vulnerability has been resolved:
|
|
|
|
scsi: pm80xx: Avoid leaking tags when processing OPC_INB_SET_CONTROLLER_CONFIG command
|
|
|
|
Tags allocated for OPC_INB_SET_CONTROLLER_CONFIG command need to be freed
|
|
when we receive the response.</Note>
|
|
</Notes>
|
|
<ReleaseDate>2024-04-19</ReleaseDate>
|
|
<CVE>CVE-2023-52500</CVE>
|
|
<ProductStatuses>
|
|
<Status Type="Fixed">
|
|
<ProductID>openEuler-20.03-LTS-SP4</ProductID>
|
|
</Status>
|
|
</ProductStatuses>
|
|
<Threats>
|
|
<Threat Type="Impact">
|
|
<Description>Low</Description>
|
|
</Threat>
|
|
</Threats>
|
|
<CVSSScoreSets>
|
|
<ScoreSet>
|
|
<BaseScore>3.3</BaseScore>
|
|
<Vector>AV:L/AC:L/PR:L/UI:N/S:U/C:L/I:N/A:N</Vector>
|
|
</ScoreSet>
|
|
</CVSSScoreSets>
|
|
<Remediations>
|
|
<Remediation Type="Vendor Fix">
|
|
<Description>kernel security update</Description>
|
|
<DATE>2024-04-19</DATE>
|
|
<URL>https://www.openeuler.org/en/security/safety-bulletin/detail.html?id=openEuler-SA-2024-1484</URL>
|
|
</Remediation>
|
|
</Remediations>
|
|
</Vulnerability>
|
|
<Vulnerability Ordinal="33" xmlns="http://www.icasi.org/CVRF/schema/vuln/1.1">
|
|
<Notes>
|
|
<Note Title="Vulnerability Description" Type="General" Ordinal="33" xml:lang="en">In the Linux kernel, the following vulnerability has been resolved:
|
|
|
|
nfc: nci: assert requested protocol is valid
|
|
|
|
The protocol is used in a bit mask to determine if the protocol is
|
|
supported. Assert the provided protocol is less than the maximum
|
|
defined so it doesn't potentially perform a shift-out-of-bounds and
|
|
provide a clearer error for undefined protocols vs unsupported ones.</Note>
|
|
</Notes>
|
|
<ReleaseDate>2024-04-19</ReleaseDate>
|
|
<CVE>CVE-2023-52507</CVE>
|
|
<ProductStatuses>
|
|
<Status Type="Fixed">
|
|
<ProductID>openEuler-20.03-LTS-SP4</ProductID>
|
|
</Status>
|
|
</ProductStatuses>
|
|
<Threats>
|
|
<Threat Type="Impact">
|
|
<Description>Medium</Description>
|
|
</Threat>
|
|
</Threats>
|
|
<CVSSScoreSets>
|
|
<ScoreSet>
|
|
<BaseScore>5.7</BaseScore>
|
|
<Vector>AV:A/AC:L/PR:N/UI:R/S:U/C:N/I:N/A:H</Vector>
|
|
</ScoreSet>
|
|
</CVSSScoreSets>
|
|
<Remediations>
|
|
<Remediation Type="Vendor Fix">
|
|
<Description>kernel security update</Description>
|
|
<DATE>2024-04-19</DATE>
|
|
<URL>https://www.openeuler.org/en/security/safety-bulletin/detail.html?id=openEuler-SA-2024-1484</URL>
|
|
</Remediation>
|
|
</Remediations>
|
|
</Vulnerability>
|
|
<Vulnerability Ordinal="34" xmlns="http://www.icasi.org/CVRF/schema/vuln/1.1">
|
|
<Notes>
|
|
<Note Title="Vulnerability Description" Type="General" Ordinal="34" xml:lang="en">In the Linux kernel, the following vulnerability has been resolved:
|
|
|
|
ieee802154: ca8210: Fix a potential UAF in ca8210_probe
|
|
|
|
If of_clk_add_provider() fails in ca8210_register_ext_clock(),
|
|
it calls clk_unregister() to release priv->clk and returns an
|
|
error. However, the caller ca8210_probe() then calls ca8210_remove(),
|
|
where priv->clk is freed again in ca8210_unregister_ext_clock(). In
|
|
this case, a use-after-free may happen in the second time we call
|
|
clk_unregister().
|
|
|
|
Fix this by removing the first clk_unregister(). Also, priv->clk could
|
|
be an error code on failure of clk_register_fixed_rate(). Use
|
|
IS_ERR_OR_NULL to catch this case in ca8210_unregister_ext_clock().</Note>
|
|
</Notes>
|
|
<ReleaseDate>2024-04-19</ReleaseDate>
|
|
<CVE>CVE-2023-52510</CVE>
|
|
<ProductStatuses>
|
|
<Status Type="Fixed">
|
|
<ProductID>openEuler-20.03-LTS-SP4</ProductID>
|
|
</Status>
|
|
</ProductStatuses>
|
|
<Threats>
|
|
<Threat Type="Impact">
|
|
<Description>Medium</Description>
|
|
</Threat>
|
|
</Threats>
|
|
<CVSSScoreSets>
|
|
<ScoreSet>
|
|
<BaseScore>6.7</BaseScore>
|
|
<Vector>AV:L/AC:L/PR:H/UI:N/S:U/C:H/I:H/A:H</Vector>
|
|
</ScoreSet>
|
|
</CVSSScoreSets>
|
|
<Remediations>
|
|
<Remediation Type="Vendor Fix">
|
|
<Description>kernel security update</Description>
|
|
<DATE>2024-04-19</DATE>
|
|
<URL>https://www.openeuler.org/en/security/safety-bulletin/detail.html?id=openEuler-SA-2024-1484</URL>
|
|
</Remediation>
|
|
</Remediations>
|
|
</Vulnerability>
|
|
<Vulnerability Ordinal="35" xmlns="http://www.icasi.org/CVRF/schema/vuln/1.1">
|
|
<Notes>
|
|
<Note Title="Vulnerability Description" Type="General" Ordinal="35" xml:lang="en">In the Linux kernel, the following vulnerability has been resolved:
|
|
|
|
RDMA/srp: Do not call scsi_done() from srp_abort()
|
|
|
|
After scmd_eh_abort_handler() has called the SCSI LLD eh_abort_handler
|
|
callback, it performs one of the following actions:
|
|
* Call scsi_queue_insert().
|
|
* Call scsi_finish_command().
|
|
* Call scsi_eh_scmd_add().
|
|
Hence, SCSI abort handlers must not call scsi_done(). Otherwise all
|
|
the above actions would trigger a use-after-free. Hence remove the
|
|
scsi_done() call from srp_abort(). Keep the srp_free_req() call
|
|
before returning SUCCESS because we may not see the command again if
|
|
SUCCESS is returned.</Note>
|
|
</Notes>
|
|
<ReleaseDate>2024-04-19</ReleaseDate>
|
|
<CVE>CVE-2023-52515</CVE>
|
|
<ProductStatuses>
|
|
<Status Type="Fixed">
|
|
<ProductID>openEuler-20.03-LTS-SP4</ProductID>
|
|
</Status>
|
|
</ProductStatuses>
|
|
<Threats>
|
|
<Threat Type="Impact">
|
|
<Description>Medium</Description>
|
|
</Threat>
|
|
</Threats>
|
|
<CVSSScoreSets>
|
|
<ScoreSet>
|
|
<BaseScore>5.5</BaseScore>
|
|
<Vector>AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H</Vector>
|
|
</ScoreSet>
|
|
</CVSSScoreSets>
|
|
<Remediations>
|
|
<Remediation Type="Vendor Fix">
|
|
<Description>kernel security update</Description>
|
|
<DATE>2024-04-19</DATE>
|
|
<URL>https://www.openeuler.org/en/security/safety-bulletin/detail.html?id=openEuler-SA-2024-1484</URL>
|
|
</Remediation>
|
|
</Remediations>
|
|
</Vulnerability>
|
|
<Vulnerability Ordinal="36" xmlns="http://www.icasi.org/CVRF/schema/vuln/1.1">
|
|
<Notes>
|
|
<Note Title="Vulnerability Description" Type="General" Ordinal="36" xml:lang="en">In the Linux kernel, the following vulnerability has been resolved:
|
|
|
|
net: fix possible store tearing in neigh_periodic_work()
|
|
|
|
While looking at a related syzbot report involving neigh_periodic_work(),
|
|
I found that I forgot to add an annotation when deleting an
|
|
RCU protected item from a list.
|
|
|
|
Readers use rcu_deference(*np), we need to use either
|
|
rcu_assign_pointer() or WRITE_ONCE() on writer side
|
|
to prevent store tearing.
|
|
|
|
I use rcu_assign_pointer() to have lockdep support,
|
|
this was the choice made in neigh_flush_dev().</Note>
|
|
</Notes>
|
|
<ReleaseDate>2024-04-19</ReleaseDate>
|
|
<CVE>CVE-2023-52522</CVE>
|
|
<ProductStatuses>
|
|
<Status Type="Fixed">
|
|
<ProductID>openEuler-20.03-LTS-SP4</ProductID>
|
|
</Status>
|
|
</ProductStatuses>
|
|
<Threats>
|
|
<Threat Type="Impact">
|
|
<Description>Medium</Description>
|
|
</Threat>
|
|
</Threats>
|
|
<CVSSScoreSets>
|
|
<ScoreSet>
|
|
<BaseScore>5.5</BaseScore>
|
|
<Vector>AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H</Vector>
|
|
</ScoreSet>
|
|
</CVSSScoreSets>
|
|
<Remediations>
|
|
<Remediation Type="Vendor Fix">
|
|
<Description>kernel security update</Description>
|
|
<DATE>2024-04-19</DATE>
|
|
<URL>https://www.openeuler.org/en/security/safety-bulletin/detail.html?id=openEuler-SA-2024-1484</URL>
|
|
</Remediation>
|
|
</Remediations>
|
|
</Vulnerability>
|
|
<Vulnerability Ordinal="37" xmlns="http://www.icasi.org/CVRF/schema/vuln/1.1">
|
|
<Notes>
|
|
<Note Title="Vulnerability Description" Type="General" Ordinal="37" xml:lang="en">In the Linux kernel, the following vulnerability has been resolved:
|
|
|
|
wifi: mac80211: fix potential key use-after-free
|
|
|
|
When ieee80211_key_link() is called by ieee80211_gtk_rekey_add()
|
|
but returns 0 due to KRACK protection (identical key reinstall),
|
|
ieee80211_gtk_rekey_add() will still return a pointer into the
|
|
key, in a potential use-after-free. This normally doesn't happen
|
|
since it's only called by iwlwifi in case of WoWLAN rekey offload
|
|
which has its own KRACK protection, but still better to fix, do
|
|
that by returning an error code and converting that to success on
|
|
the cfg80211 boundary only, leaving the error for bad callers of
|
|
ieee80211_gtk_rekey_add().</Note>
|
|
</Notes>
|
|
<ReleaseDate>2024-04-19</ReleaseDate>
|
|
<CVE>CVE-2023-52530</CVE>
|
|
<ProductStatuses>
|
|
<Status Type="Fixed">
|
|
<ProductID>openEuler-20.03-LTS-SP4</ProductID>
|
|
</Status>
|
|
</ProductStatuses>
|
|
<Threats>
|
|
<Threat Type="Impact">
|
|
<Description>Medium</Description>
|
|
</Threat>
|
|
</Threats>
|
|
<CVSSScoreSets>
|
|
<ScoreSet>
|
|
<BaseScore>5.5</BaseScore>
|
|
<Vector>AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H</Vector>
|
|
</ScoreSet>
|
|
</CVSSScoreSets>
|
|
<Remediations>
|
|
<Remediation Type="Vendor Fix">
|
|
<Description>kernel security update</Description>
|
|
<DATE>2024-04-19</DATE>
|
|
<URL>https://www.openeuler.org/en/security/safety-bulletin/detail.html?id=openEuler-SA-2024-1484</URL>
|
|
</Remediation>
|
|
</Remediations>
|
|
</Vulnerability>
|
|
<Vulnerability Ordinal="38" xmlns="http://www.icasi.org/CVRF/schema/vuln/1.1">
|
|
<Notes>
|
|
<Note Title="Vulnerability Description" Type="General" Ordinal="38" xml:lang="en">In the Linux kernel, the following vulnerability has been resolved:
|
|
|
|
nilfs2: fix potential use after free in nilfs_gccache_submit_read_data()
|
|
|
|
In nilfs_gccache_submit_read_data(), brelse(bh) is called to drop the
|
|
reference count of bh when the call to nilfs_dat_translate() fails. If
|
|
the reference count hits 0 and its owner page gets unlocked, bh may be
|
|
freed. However, bh->b_page is dereferenced to put the page after that,
|
|
which may result in a use-after-free bug. This patch moves the release
|
|
operation after unlocking and putting the page.
|
|
|
|
NOTE: The function in question is only called in GC, and in combination
|
|
with current userland tools, address translation using DAT does not occur
|
|
in that function, so the code path that causes this issue will not be
|
|
executed. However, it is possible to run that code path by intentionally
|
|
modifying the userland GC library or by calling the GC ioctl directly.
|
|
|
|
[konishi.ryusuke@gmail.com: NOTE added to the commit log]</Note>
|
|
</Notes>
|
|
<ReleaseDate>2024-04-19</ReleaseDate>
|
|
<CVE>CVE-2023-52566</CVE>
|
|
<ProductStatuses>
|
|
<Status Type="Fixed">
|
|
<ProductID>openEuler-20.03-LTS-SP4</ProductID>
|
|
</Status>
|
|
</ProductStatuses>
|
|
<Threats>
|
|
<Threat Type="Impact">
|
|
<Description>Medium</Description>
|
|
</Threat>
|
|
</Threats>
|
|
<CVSSScoreSets>
|
|
<ScoreSet>
|
|
<BaseScore>5.5</BaseScore>
|
|
<Vector>AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H</Vector>
|
|
</ScoreSet>
|
|
</CVSSScoreSets>
|
|
<Remediations>
|
|
<Remediation Type="Vendor Fix">
|
|
<Description>kernel security update</Description>
|
|
<DATE>2024-04-19</DATE>
|
|
<URL>https://www.openeuler.org/en/security/safety-bulletin/detail.html?id=openEuler-SA-2024-1484</URL>
|
|
</Remediation>
|
|
</Remediations>
|
|
</Vulnerability>
|
|
<Vulnerability Ordinal="39" xmlns="http://www.icasi.org/CVRF/schema/vuln/1.1">
|
|
<Notes>
|
|
<Note Title="Vulnerability Description" Type="General" Ordinal="39" xml:lang="en">In the Linux kernel, the following vulnerability has been resolved:
|
|
|
|
net: bridge: use DEV_STATS_INC()
|
|
|
|
syzbot/KCSAN reported data-races in br_handle_frame_finish() [1]
|
|
This function can run from multiple cpus without mutual exclusion.
|
|
|
|
Adopt SMP safe DEV_STATS_INC() to update dev->stats fields.
|
|
|
|
Handles updates to dev->stats.tx_dropped while we are at it.
|
|
|
|
[1]
|
|
BUG: KCSAN: data-race in br_handle_frame_finish / br_handle_frame_finish
|
|
|
|
read-write to 0xffff8881374b2178 of 8 bytes by interrupt on cpu 1:
|
|
br_handle_frame_finish+0xd4f/0xef0 net/bridge/br_input.c:189
|
|
br_nf_hook_thresh+0x1ed/0x220
|
|
br_nf_pre_routing_finish_ipv6+0x50f/0x540
|
|
NF_HOOK include/linux/netfilter.h:304 [inline]
|
|
br_nf_pre_routing_ipv6+0x1e3/0x2a0 net/bridge/br_netfilter_ipv6.c:178
|
|
br_nf_pre_routing+0x526/0xba0 net/bridge/br_netfilter_hooks.c:508
|
|
nf_hook_entry_hookfn include/linux/netfilter.h:144 [inline]
|
|
nf_hook_bridge_pre net/bridge/br_input.c:272 [inline]
|
|
br_handle_frame+0x4c9/0x940 net/bridge/br_input.c:417
|
|
__netif_receive_skb_core+0xa8a/0x21e0 net/core/dev.c:5417
|
|
__netif_receive_skb_one_core net/core/dev.c:5521 [inline]
|
|
__netif_receive_skb+0x57/0x1b0 net/core/dev.c:5637
|
|
process_backlog+0x21f/0x380 net/core/dev.c:5965
|
|
__napi_poll+0x60/0x3b0 net/core/dev.c:6527
|
|
napi_poll net/core/dev.c:6594 [inline]
|
|
net_rx_action+0x32b/0x750 net/core/dev.c:6727
|
|
__do_softirq+0xc1/0x265 kernel/softirq.c:553
|
|
run_ksoftirqd+0x17/0x20 kernel/softirq.c:921
|
|
smpboot_thread_fn+0x30a/0x4a0 kernel/smpboot.c:164
|
|
kthread+0x1d7/0x210 kernel/kthread.c:388
|
|
ret_from_fork+0x48/0x60 arch/x86/kernel/process.c:147
|
|
ret_from_fork_asm+0x11/0x20 arch/x86/entry/entry_64.S:304
|
|
|
|
read-write to 0xffff8881374b2178 of 8 bytes by interrupt on cpu 0:
|
|
br_handle_frame_finish+0xd4f/0xef0 net/bridge/br_input.c:189
|
|
br_nf_hook_thresh+0x1ed/0x220
|
|
br_nf_pre_routing_finish_ipv6+0x50f/0x540
|
|
NF_HOOK include/linux/netfilter.h:304 [inline]
|
|
br_nf_pre_routing_ipv6+0x1e3/0x2a0 net/bridge/br_netfilter_ipv6.c:178
|
|
br_nf_pre_routing+0x526/0xba0 net/bridge/br_netfilter_hooks.c:508
|
|
nf_hook_entry_hookfn include/linux/netfilter.h:144 [inline]
|
|
nf_hook_bridge_pre net/bridge/br_input.c:272 [inline]
|
|
br_handle_frame+0x4c9/0x940 net/bridge/br_input.c:417
|
|
__netif_receive_skb_core+0xa8a/0x21e0 net/core/dev.c:5417
|
|
__netif_receive_skb_one_core net/core/dev.c:5521 [inline]
|
|
__netif_receive_skb+0x57/0x1b0 net/core/dev.c:5637
|
|
process_backlog+0x21f/0x380 net/core/dev.c:5965
|
|
__napi_poll+0x60/0x3b0 net/core/dev.c:6527
|
|
napi_poll net/core/dev.c:6594 [inline]
|
|
net_rx_action+0x32b/0x750 net/core/dev.c:6727
|
|
__do_softirq+0xc1/0x265 kernel/softirq.c:553
|
|
do_softirq+0x5e/0x90 kernel/softirq.c:454
|
|
__local_bh_enable_ip+0x64/0x70 kernel/softirq.c:381
|
|
__raw_spin_unlock_bh include/linux/spinlock_api_smp.h:167 [inline]
|
|
_raw_spin_unlock_bh+0x36/0x40 kernel/locking/spinlock.c:210
|
|
spin_unlock_bh include/linux/spinlock.h:396 [inline]
|
|
batadv_tt_local_purge+0x1a8/0x1f0 net/batman-adv/translation-table.c:1356
|
|
batadv_tt_purge+0x2b/0x630 net/batman-adv/translation-table.c:3560
|
|
process_one_work kernel/workqueue.c:2630 [inline]
|
|
process_scheduled_works+0x5b8/0xa30 kernel/workqueue.c:2703
|
|
worker_thread+0x525/0x730 kernel/workqueue.c:2784
|
|
kthread+0x1d7/0x210 kernel/kthread.c:388
|
|
ret_from_fork+0x48/0x60 arch/x86/kernel/process.c:147
|
|
ret_from_fork_asm+0x11/0x20 arch/x86/entry/entry_64.S:304
|
|
|
|
value changed: 0x00000000000d7190 -> 0x00000000000d7191
|
|
|
|
Reported by Kernel Concurrency Sanitizer on:
|
|
CPU: 0 PID: 14848 Comm: kworker/u4:11 Not tainted 6.6.0-rc1-syzkaller-00236-gad8a69f361b9 #0</Note>
|
|
</Notes>
|
|
<ReleaseDate>2024-04-19</ReleaseDate>
|
|
<CVE>CVE-2023-52578</CVE>
|
|
<ProductStatuses>
|
|
<Status Type="Fixed">
|
|
<ProductID>openEuler-20.03-LTS-SP4</ProductID>
|
|
</Status>
|
|
</ProductStatuses>
|
|
<Threats>
|
|
<Threat Type="Impact">
|
|
<Description>Medium</Description>
|
|
</Threat>
|
|
</Threats>
|
|
<CVSSScoreSets>
|
|
<ScoreSet>
|
|
<BaseScore>5.5</BaseScore>
|
|
<Vector>AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H</Vector>
|
|
</ScoreSet>
|
|
</CVSSScoreSets>
|
|
<Remediations>
|
|
<Remediation Type="Vendor Fix">
|
|
<Description>kernel security update</Description>
|
|
<DATE>2024-04-19</DATE>
|
|
<URL>https://www.openeuler.org/en/security/safety-bulletin/detail.html?id=openEuler-SA-2024-1484</URL>
|
|
</Remediation>
|
|
</Remediations>
|
|
</Vulnerability>
|
|
<Vulnerability Ordinal="40" xmlns="http://www.icasi.org/CVRF/schema/vuln/1.1">
|
|
<Notes>
|
|
<Note Title="Vulnerability Description" Type="General" Ordinal="40" xml:lang="en">In the Linux kernel, the following vulnerability has been resolved:
|
|
|
|
ceph: fix deadlock or deadcode of misusing dget()
|
|
|
|
The lock order is incorrect between denty and its parent, we should
|
|
always make sure that the parent get the lock first.
|
|
|
|
But since this deadcode is never used and the parent dir will always
|
|
be set from the callers, let's just remove it.</Note>
|
|
</Notes>
|
|
<ReleaseDate>2024-04-19</ReleaseDate>
|
|
<CVE>CVE-2023-52583</CVE>
|
|
<ProductStatuses>
|
|
<Status Type="Fixed">
|
|
<ProductID>openEuler-20.03-LTS-SP4</ProductID>
|
|
</Status>
|
|
</ProductStatuses>
|
|
<Threats>
|
|
<Threat Type="Impact">
|
|
<Description>Medium</Description>
|
|
</Threat>
|
|
</Threats>
|
|
<CVSSScoreSets>
|
|
<ScoreSet>
|
|
<BaseScore>5.5</BaseScore>
|
|
<Vector>AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H</Vector>
|
|
</ScoreSet>
|
|
</CVSSScoreSets>
|
|
<Remediations>
|
|
<Remediation Type="Vendor Fix">
|
|
<Description>kernel security update</Description>
|
|
<DATE>2024-04-19</DATE>
|
|
<URL>https://www.openeuler.org/en/security/safety-bulletin/detail.html?id=openEuler-SA-2024-1484</URL>
|
|
</Remediation>
|
|
</Remediations>
|
|
</Vulnerability>
|
|
<Vulnerability Ordinal="41" xmlns="http://www.icasi.org/CVRF/schema/vuln/1.1">
|
|
<Notes>
|
|
<Note Title="Vulnerability Description" Type="General" Ordinal="41" xml:lang="en">In the Linux kernel, the following vulnerability has been resolved:
|
|
|
|
IB/ipoib: Fix mcast list locking
|
|
|
|
Releasing the `priv->lock` while iterating the `priv->multicast_list` in
|
|
`ipoib_mcast_join_task()` opens a window for `ipoib_mcast_dev_flush()` to
|
|
remove the items while in the middle of iteration. If the mcast is removed
|
|
while the lock was dropped, the for loop spins forever resulting in a hard
|
|
lockup (as was reported on RHEL 4.18.0-372.75.1.el8_6 kernel):
|
|
|
|
Task A (kworker/u72:2 below) | Task B (kworker/u72:0 below)
|
|
-----------------------------------+-----------------------------------
|
|
ipoib_mcast_join_task(work) | ipoib_ib_dev_flush_light(work)
|
|
spin_lock_irq(&priv->lock) | __ipoib_ib_dev_flush(priv, ...)
|
|
list_for_each_entry(mcast, | ipoib_mcast_dev_flush(dev = priv->dev)
|
|
&priv->multicast_list, list) |
|
|
ipoib_mcast_join(dev, mcast) |
|
|
spin_unlock_irq(&priv->lock) |
|
|
| spin_lock_irqsave(&priv->lock, flags)
|
|
| list_for_each_entry_safe(mcast, tmcast,
|
|
| &priv->multicast_list, list)
|
|
| list_del(&mcast->list);
|
|
| list_add_tail(&mcast->list, &remove_list)
|
|
| spin_unlock_irqrestore(&priv->lock, flags)
|
|
spin_lock_irq(&priv->lock) |
|
|
| ipoib_mcast_remove_list(&remove_list)
|
|
(Here, `mcast` is no longer on the | list_for_each_entry_safe(mcast, tmcast,
|
|
`priv->multicast_list` and we keep | remove_list, list)
|
|
spinning on the `remove_list` of | >>> wait_for_completion(&mcast->done)
|
|
the other thread which is blocked |
|
|
and the list is still valid on |
|
|
it's stack.)
|
|
|
|
Fix this by keeping the lock held and changing to GFP_ATOMIC to prevent
|
|
eventual sleeps.
|
|
Unfortunately we could not reproduce the lockup and confirm this fix but
|
|
based on the code review I think this fix should address such lockups.
|
|
|
|
crash> bc 31
|
|
PID: 747 TASK: ff1c6a1a007e8000 CPU: 31 COMMAND: "kworker/u72:2"
|
|
--
|
|
[exception RIP: ipoib_mcast_join_task+0x1b1]
|
|
RIP: ffffffffc0944ac1 RSP: ff646f199a8c7e00 RFLAGS: 00000002
|
|
RAX: 0000000000000000 RBX: ff1c6a1a04dc82f8 RCX: 0000000000000000
|
|
work (&priv->mcast_task{,.work})
|
|
RDX: ff1c6a192d60ac68 RSI: 0000000000000286 RDI: ff1c6a1a04dc8000
|
|
&mcast->list
|
|
RBP: ff646f199a8c7e90 R8: ff1c699980019420 R9: ff1c6a1920c9a000
|
|
R10: ff646f199a8c7e00 R11: ff1c6a191a7d9800 R12: ff1c6a192d60ac00
|
|
mcast
|
|
R13: ff1c6a1d82200000 R14: ff1c6a1a04dc8000 R15: ff1c6a1a04dc82d8
|
|
dev priv (&priv->lock) &priv->multicast_list (aka head)
|
|
ORIG_RAX: ffffffffffffffff CS: 0010 SS: 0018
|
|
--- <NMI exception stack> ---
|
|
#5 [ff646f199a8c7e00] ipoib_mcast_join_task+0x1b1 at ffffffffc0944ac1 [ib_ipoib]
|
|
#6 [ff646f199a8c7e98] process_one_work+0x1a7 at ffffffff9bf10967
|
|
|
|
crash> rx ff646f199a8c7e68
|
|
ff646f199a8c7e68: ff1c6a1a04dc82f8 <<< work = &priv->mcast_task.work
|
|
|
|
crash> list -hO ipoib_dev_priv.multicast_list ff1c6a1a04dc8000
|
|
(empty)
|
|
|
|
crash> ipoib_dev_priv.mcast_task.work.func,mcast_mutex.owner.counter ff1c6a1a04dc8000
|
|
mcast_task.work.func = 0xffffffffc0944910 <ipoib_mcast_join_task>,
|
|
mcast_mutex.owner.counter = 0xff1c69998efec000
|
|
|
|
crash> b 8
|
|
PID: 8 TASK: ff1c69998efec000 CPU: 33 COMMAND: "kworker/u72:0"
|
|
--
|
|
#3 [ff646f1980153d50] wait_for_completion+0x96 at ffffffff9c7d7646
|
|
#4 [ff646f1980153d90] ipoib_mcast_remove_list+0x56 at ffffffffc0944dc6 [ib_ipoib]
|
|
#5 [ff646f1980153de8] ipoib_mcast_dev_flush+0x1a7 at ffffffffc09455a7 [ib_ipoib]
|
|
#6 [ff646f1980153e58] __ipoib_ib_dev_flush+0x1a4 at ffffffffc09431a4 [ib_ipoib]
|
|
#7 [ff
|
|
---truncated---</Note>
|
|
</Notes>
|
|
<ReleaseDate>2024-04-19</ReleaseDate>
|
|
<CVE>CVE-2023-52587</CVE>
|
|
<ProductStatuses>
|
|
<Status Type="Fixed">
|
|
<ProductID>openEuler-20.03-LTS-SP4</ProductID>
|
|
</Status>
|
|
</ProductStatuses>
|
|
<Threats>
|
|
<Threat Type="Impact">
|
|
<Description>Medium</Description>
|
|
</Threat>
|
|
</Threats>
|
|
<CVSSScoreSets>
|
|
<ScoreSet>
|
|
<BaseScore>4.7</BaseScore>
|
|
<Vector>AV:L/AC:H/PR:L/UI:N/S:U/C:N/I:N/A:H</Vector>
|
|
</ScoreSet>
|
|
</CVSSScoreSets>
|
|
<Remediations>
|
|
<Remediation Type="Vendor Fix">
|
|
<Description>kernel security update</Description>
|
|
<DATE>2024-04-19</DATE>
|
|
<URL>https://www.openeuler.org/en/security/safety-bulletin/detail.html?id=openEuler-SA-2024-1484</URL>
|
|
</Remediation>
|
|
</Remediations>
|
|
</Vulnerability>
|
|
<Vulnerability Ordinal="42" xmlns="http://www.icasi.org/CVRF/schema/vuln/1.1">
|
|
<Notes>
|
|
<Note Title="Vulnerability Description" Type="General" Ordinal="42" xml:lang="en">In the Linux kernel, the following vulnerability has been resolved:
|
|
|
|
wifi: ath9k: Fix potential array-index-out-of-bounds read in ath9k_htc_txstatus()
|
|
|
|
Fix an array-index-out-of-bounds read in ath9k_htc_txstatus(). The bug
|
|
occurs when txs->cnt, data from a URB provided by a USB device, is
|
|
bigger than the size of the array txs->txstatus, which is
|
|
HTC_MAX_TX_STATUS. WARN_ON() already checks it, but there is no bug
|
|
handling code after the check. Make the function return if that is the
|
|
case.
|
|
|
|
Found by a modified version of syzkaller.
|
|
|
|
UBSAN: array-index-out-of-bounds in htc_drv_txrx.c
|
|
index 13 is out of range for type '__wmi_event_txstatus [12]'
|
|
Call Trace:
|
|
ath9k_htc_txstatus
|
|
ath9k_wmi_event_tasklet
|
|
tasklet_action_common
|
|
__do_softirq
|
|
irq_exit_rxu
|
|
sysvec_apic_timer_interrupt</Note>
|
|
</Notes>
|
|
<ReleaseDate>2024-04-19</ReleaseDate>
|
|
<CVE>CVE-2023-52594</CVE>
|
|
<ProductStatuses>
|
|
<Status Type="Fixed">
|
|
<ProductID>openEuler-20.03-LTS-SP4</ProductID>
|
|
</Status>
|
|
</ProductStatuses>
|
|
<Threats>
|
|
<Threat Type="Impact">
|
|
<Description>Medium</Description>
|
|
</Threat>
|
|
</Threats>
|
|
<CVSSScoreSets>
|
|
<ScoreSet>
|
|
<BaseScore>4.4</BaseScore>
|
|
<Vector>AV:L/AC:L/PR:H/UI:N/S:U/C:N/I:N/A:H</Vector>
|
|
</ScoreSet>
|
|
</CVSSScoreSets>
|
|
<Remediations>
|
|
<Remediation Type="Vendor Fix">
|
|
<Description>kernel security update</Description>
|
|
<DATE>2024-04-19</DATE>
|
|
<URL>https://www.openeuler.org/en/security/safety-bulletin/detail.html?id=openEuler-SA-2024-1484</URL>
|
|
</Remediation>
|
|
</Remediations>
|
|
</Vulnerability>
|
|
<Vulnerability Ordinal="43" xmlns="http://www.icasi.org/CVRF/schema/vuln/1.1">
|
|
<Notes>
|
|
<Note Title="Vulnerability Description" Type="General" Ordinal="43" xml:lang="en">In the Linux kernel, the following vulnerability has been resolved:
|
|
|
|
wifi: rt2x00: restart beacon queue when hardware reset
|
|
|
|
When a hardware reset is triggered, all registers are reset, so all
|
|
queues are forced to stop in hardware interface. However, mac80211
|
|
will not automatically stop the queue. If we don't manually stop the
|
|
beacon queue, the queue will be deadlocked and unable to start again.
|
|
This patch fixes the issue where Apple devices cannot connect to the
|
|
AP after calling ieee80211_restart_hw().</Note>
|
|
</Notes>
|
|
<ReleaseDate>2024-04-19</ReleaseDate>
|
|
<CVE>CVE-2023-52595</CVE>
|
|
<ProductStatuses>
|
|
<Status Type="Fixed">
|
|
<ProductID>openEuler-20.03-LTS-SP4</ProductID>
|
|
</Status>
|
|
</ProductStatuses>
|
|
<Threats>
|
|
<Threat Type="Impact">
|
|
<Description>Medium</Description>
|
|
</Threat>
|
|
</Threats>
|
|
<CVSSScoreSets>
|
|
<ScoreSet>
|
|
<BaseScore>4.4</BaseScore>
|
|
<Vector>AV:L/AC:L/PR:H/UI:N/S:U/C:N/I:N/A:H</Vector>
|
|
</ScoreSet>
|
|
</CVSSScoreSets>
|
|
<Remediations>
|
|
<Remediation Type="Vendor Fix">
|
|
<Description>kernel security update</Description>
|
|
<DATE>2024-04-19</DATE>
|
|
<URL>https://www.openeuler.org/en/security/safety-bulletin/detail.html?id=openEuler-SA-2024-1484</URL>
|
|
</Remediation>
|
|
</Remediations>
|
|
</Vulnerability>
|
|
<Vulnerability Ordinal="44" xmlns="http://www.icasi.org/CVRF/schema/vuln/1.1">
|
|
<Notes>
|
|
<Note Title="Vulnerability Description" Type="General" Ordinal="44" xml:lang="en">In the Linux kernel, the following vulnerability has been resolved:
|
|
|
|
KVM: s390: fix setting of fpc register
|
|
|
|
kvm_arch_vcpu_ioctl_set_fpu() allows to set the floating point control
|
|
(fpc) register of a guest cpu. The new value is tested for validity by
|
|
temporarily loading it into the fpc register.
|
|
|
|
This may lead to corruption of the fpc register of the host process:
|
|
if an interrupt happens while the value is temporarily loaded into the fpc
|
|
register, and within interrupt context floating point or vector registers
|
|
are used, the current fp/vx registers are saved with save_fpu_regs()
|
|
assuming they belong to user space and will be loaded into fp/vx registers
|
|
when returning to user space.
|
|
|
|
test_fp_ctl() restores the original user space / host process fpc register
|
|
value, however it will be discarded, when returning to user space.
|
|
|
|
In result the host process will incorrectly continue to run with the value
|
|
that was supposed to be used for a guest cpu.
|
|
|
|
Fix this by simply removing the test. There is another test right before
|
|
the SIE context is entered which will handles invalid values.
|
|
|
|
This results in a change of behaviour: invalid values will now be accepted
|
|
instead of that the ioctl fails with -EINVAL. This seems to be acceptable,
|
|
given that this interface is most likely not used anymore, and this is in
|
|
addition the same behaviour implemented with the memory mapped interface
|
|
(replace invalid values with zero) - see sync_regs() in kvm-s390.c.</Note>
|
|
</Notes>
|
|
<ReleaseDate>2024-04-19</ReleaseDate>
|
|
<CVE>CVE-2023-52597</CVE>
|
|
<ProductStatuses>
|
|
<Status Type="Fixed">
|
|
<ProductID>openEuler-20.03-LTS-SP4</ProductID>
|
|
</Status>
|
|
</ProductStatuses>
|
|
<Threats>
|
|
<Threat Type="Impact">
|
|
<Description>Medium</Description>
|
|
</Threat>
|
|
</Threats>
|
|
<CVSSScoreSets>
|
|
<ScoreSet>
|
|
<BaseScore>4.7</BaseScore>
|
|
<Vector>AV:L/AC:H/PR:H/UI:N/S:U/C:N/I:L/A:H</Vector>
|
|
</ScoreSet>
|
|
</CVSSScoreSets>
|
|
<Remediations>
|
|
<Remediation Type="Vendor Fix">
|
|
<Description>kernel security update</Description>
|
|
<DATE>2024-04-19</DATE>
|
|
<URL>https://www.openeuler.org/en/security/safety-bulletin/detail.html?id=openEuler-SA-2024-1484</URL>
|
|
</Remediation>
|
|
</Remediations>
|
|
</Vulnerability>
|
|
<Vulnerability Ordinal="45" xmlns="http://www.icasi.org/CVRF/schema/vuln/1.1">
|
|
<Notes>
|
|
<Note Title="Vulnerability Description" Type="General" Ordinal="45" xml:lang="en">In the Linux kernel, the following vulnerability has been resolved:
|
|
|
|
s390/ptrace: handle setting of fpc register correctly
|
|
|
|
If the content of the floating point control (fpc) register of a traced
|
|
process is modified with the ptrace interface the new value is tested for
|
|
validity by temporarily loading it into the fpc register.
|
|
|
|
This may lead to corruption of the fpc register of the tracing process:
|
|
if an interrupt happens while the value is temporarily loaded into the
|
|
fpc register, and within interrupt context floating point or vector
|
|
registers are used, the current fp/vx registers are saved with
|
|
save_fpu_regs() assuming they belong to user space and will be loaded into
|
|
fp/vx registers when returning to user space.
|
|
|
|
test_fp_ctl() restores the original user space fpc register value, however
|
|
it will be discarded, when returning to user space.
|
|
|
|
In result the tracer will incorrectly continue to run with the value that
|
|
was supposed to be used for the traced process.
|
|
|
|
Fix this by saving fpu register contents with save_fpu_regs() before using
|
|
test_fp_ctl().</Note>
|
|
</Notes>
|
|
<ReleaseDate>2024-04-19</ReleaseDate>
|
|
<CVE>CVE-2023-52598</CVE>
|
|
<ProductStatuses>
|
|
<Status Type="Fixed">
|
|
<ProductID>openEuler-20.03-LTS-SP4</ProductID>
|
|
</Status>
|
|
</ProductStatuses>
|
|
<Threats>
|
|
<Threat Type="Impact">
|
|
<Description>Medium</Description>
|
|
</Threat>
|
|
</Threats>
|
|
<CVSSScoreSets>
|
|
<ScoreSet>
|
|
<BaseScore>5.5</BaseScore>
|
|
<Vector>AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H</Vector>
|
|
</ScoreSet>
|
|
</CVSSScoreSets>
|
|
<Remediations>
|
|
<Remediation Type="Vendor Fix">
|
|
<Description>kernel security update</Description>
|
|
<DATE>2024-04-19</DATE>
|
|
<URL>https://www.openeuler.org/en/security/safety-bulletin/detail.html?id=openEuler-SA-2024-1484</URL>
|
|
</Remediation>
|
|
</Remediations>
|
|
</Vulnerability>
|
|
<Vulnerability Ordinal="46" xmlns="http://www.icasi.org/CVRF/schema/vuln/1.1">
|
|
<Notes>
|
|
<Note Title="Vulnerability Description" Type="General" Ordinal="46" xml:lang="en">In the Linux kernel, the following vulnerability has been resolved:
|
|
|
|
ext4: avoid online resizing failures due to oversized flex bg
|
|
|
|
When we online resize an ext4 filesystem with a oversized flexbg_size,
|
|
|
|
mkfs.ext4 -F -G 67108864 $dev -b 4096 100M
|
|
mount $dev $dir
|
|
resize2fs $dev 16G
|
|
|
|
the following WARN_ON is triggered:
|
|
==================================================================
|
|
WARNING: CPU: 0 PID: 427 at mm/page_alloc.c:4402 __alloc_pages+0x411/0x550
|
|
Modules linked in: sg(E)
|
|
CPU: 0 PID: 427 Comm: resize2fs Tainted: G E 6.6.0-rc5+ #314
|
|
RIP: 0010:__alloc_pages+0x411/0x550
|
|
Call Trace:
|
|
<TASK>
|
|
__kmalloc_large_node+0xa2/0x200
|
|
__kmalloc+0x16e/0x290
|
|
ext4_resize_fs+0x481/0xd80
|
|
__ext4_ioctl+0x1616/0x1d90
|
|
ext4_ioctl+0x12/0x20
|
|
__x64_sys_ioctl+0xf0/0x150
|
|
do_syscall_64+0x3b/0x90
|
|
==================================================================
|
|
|
|
This is because flexbg_size is too large and the size of the new_group_data
|
|
array to be allocated exceeds MAX_ORDER. Currently, the minimum value of
|
|
MAX_ORDER is 8, the minimum value of PAGE_SIZE is 4096, the corresponding
|
|
maximum number of groups that can be allocated is:
|
|
|
|
(PAGE_SIZE << MAX_ORDER) / sizeof(struct ext4_new_group_data) ≈ 21845
|
|
|
|
And the value that is down-aligned to the power of 2 is 16384. Therefore,
|
|
this value is defined as MAX_RESIZE_BG, and the number of groups added
|
|
each time does not exceed this value during resizing, and is added multiple
|
|
times to complete the online resizing. The difference is that the metadata
|
|
in a flex_bg may be more dispersed.</Note>
|
|
</Notes>
|
|
<ReleaseDate>2024-04-19</ReleaseDate>
|
|
<CVE>CVE-2023-52622</CVE>
|
|
<ProductStatuses>
|
|
<Status Type="Fixed">
|
|
<ProductID>openEuler-20.03-LTS-SP4</ProductID>
|
|
</Status>
|
|
</ProductStatuses>
|
|
<Threats>
|
|
<Threat Type="Impact">
|
|
<Description>Medium</Description>
|
|
</Threat>
|
|
</Threats>
|
|
<CVSSScoreSets>
|
|
<ScoreSet>
|
|
<BaseScore>4.4</BaseScore>
|
|
<Vector>AV:L/AC:L/PR:H/UI:N/S:U/C:N/I:N/A:H</Vector>
|
|
</ScoreSet>
|
|
</CVSSScoreSets>
|
|
<Remediations>
|
|
<Remediation Type="Vendor Fix">
|
|
<Description>kernel security update</Description>
|
|
<DATE>2024-04-19</DATE>
|
|
<URL>https://www.openeuler.org/en/security/safety-bulletin/detail.html?id=openEuler-SA-2024-1484</URL>
|
|
</Remediation>
|
|
</Remediations>
|
|
</Vulnerability>
|
|
</cvrfdoc> |