In the Linux kernel, the following vulnerability has been resolved: btrfs: fix qgroup reserve leaks in cow_file_range In the buffered write path, the dirty page owns the qgroup reserve until it creates an ordered_extent. Therefore, any errors that occur before the ordered_extent is created must free that reservation, or else the space is leaked. The fstest generic/475 exercises various IO error paths, and is able to trigger errors in cow_file_range where we fail to get to allocating the ordered extent. Note that because we *do* clear delalloc, we are likely to remove the inode from the delalloc list, so the inodes/pages to not have invalidate/launder called on them in the commit abort path. This results in failures at the unmount stage of the test that look like: BTRFS: error (device dm-8 state EA) in cleanup_transaction:2018: errno=-5 IO failure BTRFS: error (device dm-8 state EA) in btrfs_replace_file_extents:2416: errno=-5 IO failure BTRFS warning (device dm-8 state EA): qgroup 0/5 has unreleased space, type 0 rsv 28672 ------------[ cut here ]------------ WARNING: CPU: 3 PID: 22588 at fs/btrfs/disk-io.c:4333 close_ctree+0x222/0x4d0 [btrfs] Modules linked in: btrfs blake2b_generic libcrc32c xor zstd_compress raid6_pq CPU: 3 PID: 22588 Comm: umount Kdump: loaded Tainted: G W 6.10.0-rc7-gab56fde445b8 #21 Hardware name: QEMU Standard PC (i440FX + PIIX, 1996), BIOS Arch Linux 1.16.3-1-1 04/01/2014 RIP: 0010:close_ctree+0x222/0x4d0 [btrfs] RSP: 0018:ffffb4465283be00 EFLAGS: 00010202 RAX: 0000000000000001 RBX: ffffa1a1818e1000 RCX: 0000000000000001 RDX: 0000000000000000 RSI: ffffb4465283bbe0 RDI: ffffa1a19374fcb8 RBP: ffffa1a1818e13c0 R08: 0000000100028b16 R09: 0000000000000000 R10: 0000000000000003 R11: 0000000000000003 R12: ffffa1a18ad7972c R13: 0000000000000000 R14: 0000000000000000 R15: 0000000000000000 FS: 00007f9168312b80(0000) GS:ffffa1a4afcc0000(0000) knlGS:0000000000000000 CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033 CR2: 00007f91683c9140 CR3: 000000010acaa000 CR4: 00000000000006f0 Call Trace: <TASK> ? close_ctree+0x222/0x4d0 [btrfs] ? __warn.cold+0x8e/0xea ? close_ctree+0x222/0x4d0 [btrfs] ? report_bug+0xff/0x140 ? handle_bug+0x3b/0x70 ? exc_invalid_op+0x17/0x70 ? asm_exc_invalid_op+0x1a/0x20 ? close_ctree+0x222/0x4d0 [btrfs] generic_shutdown_super+0x70/0x160 kill_anon_super+0x11/0x40 btrfs_kill_super+0x11/0x20 [btrfs] deactivate_locked_super+0x2e/0xa0 cleanup_mnt+0xb5/0x150 task_work_run+0x57/0x80 syscall_exit_to_user_mode+0x121/0x130 do_syscall_64+0xab/0x1a0 entry_SYSCALL_64_after_hwframe+0x77/0x7f RIP: 0033:0x7f916847a887 ---[ end trace 0000000000000000 ]--- BTRFS error (device dm-8 state EA): qgroup reserved space leaked Cases 2 and 3 in the out_reserve path both pertain to this type of leak and must free the reserved qgroup data. Because it is already an error path, I opted not to handle the possible errors in btrfs_free_qgroup_data.

According to the versions of the kernel packages installed, the EulerOS installation on the remote host is affected by the following vulnerabilities :

    In the Linux kernel, the following vulnerability has been resolved:ntb: intel: Fix the NULL vs IS_ERR()     bug for debugfs_create_dir()  The debugfs_create_dir() function returns error pointers. It never returns     NULL. So use IS_ERR() to check it.(CVE-2023-52917)

    tracing: Free buffers when a used dynamic event is removed(CVE-2022-49006)

    block, bfq: fix possible UAF for bfqq-bic with merge chain(CVE-2024-47706)

    In the Linux kernel, the following vulnerability has been resolved:iommu: Return right value in     iommu_sva_bind_device()  iommu_sva_bind_device() should return either a sva bond handle or an ERR_PTR     value in error cases. Existing drivers (idxd and uacce) only check the return value with IS_ERR(). This     could potentially lead to a kernel NULL pointer dereference issue if the function returns NULL instead of     an error pointer.  In reality, this doesn't cause any problems because iommu_sva_bind_device() only     returns NULL when the kernel is not configured with CONFIG_IOMMU_SVA. In this case,     iommu_dev_enable_feature(dev, IOMMU_DEV_FEAT_SVA) will return an error, and the device drivers won't call     iommu_sva_bind_device() at all.(CVE-2024-40945)

    net: hns3: void array out of bound when loop tnl_num(CVE-2024-46833)

    KVM: arm64: Make ICC_*SGI*_EL1 undef in the absence of a vGICv3(CVE-2024-46707)

    net/mlx5: Fix bridge mode operations when there are no VFs(CVE-2024-46857)

    In the Linux kernel, the following vulnerability has been resolved:netfilter: nft_socket: fix sk refcount     leaks  We must put 'sk' reference before returning.(CVE-2024-46855)

    fsnotify: clear PARENT_WATCHED flags lazily(CVE-2024-47660)

    tcp_bpf: fix return value of tcp_bpf_sendmsg()(CVE-2024-46783)

    mlxsw: spectrum_acl_erp: Fix object nesting warning(CVE-2024-43880)

    xdp: fix invalid wait context of page_pool_destroy()(CVE-2024-43834)

    virtio_net: Fix napi_skb_cache_put warning (CVE-2024-43835)

    net: hns3: fix kernel crash problem in concurrent scenario (CVE-2024-39507)

    xfrm6: check ip6_dst_idev() return value in xfrm6_get_saddr()(CVE-2024-40959)

    In the Linux kernel, the following vulnerability has been resolved:net: ena: Add validation for completion     descriptors consistency  Validate that `first` flag is set only for the first descriptor in multi-buffer     packets. In case of an invalid descriptor, a reset will occur. A new reset reason for RX data corruption     has been added.(CVE-2024-40999)

    ipvlan: Dont Use skb-sk in ipvlan_process_v{4,6}_outbound(CVE-2024-33621)

    net: relax socket state check at accept time(CVE-2024-36484)

    net: fix information leakage in /proc/ net/ptype(CVE-2022-48757)

    net: bridge: vlan: fix memory leak in __allowed_ingress(CVE-2022-48748)

    In the Linux kernel, the following vulnerability has been resolved:USB: usbtmc: prevent kernel-usb-     infoleak  The syzbot reported a kernel-usb-infoleak in usbtmc_write, we need to clear the structure before     filling fields.(CVE-2024-47671)

    hv_netvsc: Register VF in netvsc_probe(CVE-2024-26820)

    vfs: Don't evict inode under the inode lru traversing context(CVE-2024-45003)

    perf/x86/intel: Limit the period on Haswell(CVE-2024-46848)

    ethtool: fail closed if we can't get max channel used in indirection tables(CVE-2024-46834)

    ELF: fix kernel.randomize_va_space double read(CVE-2024-46826)

    arm64: acpi: Harden get_cpu_for_acpi_id() against missing CPU entry(CVE-2024-46822)

    sched/smt: Fix unbalance sched_smt_present dec/inc(CVE-2024-44958)

    platform/x86: panasonic-laptop: Fix SINF array out of bounds accesses(CVE-2024-46859)

    rtmutex: Drop rt_mutex::wait_lock before scheduling(CVE-2024-46829)

    drm/amd/display: Check num_valid_sets before accessing reader_wm_sets[](CVE-2024-46815)

    drm/amd/display: Check link_index before accessing dc-links[](CVE-2024-46813)

    drm/amd/display: Stop amdgpu_dm initialize when link nums greater than max_links(CVE-2024-46816)

    drm/amd/display: Check msg_id before processing transcation(CVE-2024-46814)

    thunderbolt: Mark XDomain as unplugged when router is removed(CVE-2024-46702)

    nvmet-tcp: fix kernel crash if commands allocation fails(CVE-2024-46737)

    of/irq: Prevent device address out-of-bounds read in interrupt map walk(CVE-2024-46743)

    VMCI: Fix use-after-free when removing resource in vmci_resource_remove()(CVE-2024-46738)

    usb: typec: ucsi: Fix null pointer dereference in trace(CVE-2024-46719)

    pktgen: use cpus_read_lock() in pg_net_init()(CVE-2024-46681)

    ethtool: check device is present when getting link settings(CVE-2024-46679)

    apparmor: fix possible NULL pointer dereference(CVE-2024-46721)

    selinux,smack: don't bypass permissions check in inode_setsecctx hook(CVE-2024-46695)

    bonding: change ipsec_lock from spin lock to mutex(CVE-2024-46678)

    PCI: Add missing bridge lock to pci_bus_lock()(CVE-2024-46750)

    ice: Add netif_device_attach/detach into PF reset flow(CVE-2024-46770)

    md: fix deadlock between mddev_suspend and flush bio(CVE-2024-43855)

    driver: iio: add missing checks on iio_info's callback access(CVE-2024-46715)

    uio_hv_generic: Fix kernel NULL pointer dereference in hv_uio_rescind (CVE-2024-46739)

    btrfs: fix qgroup reserve leaks in cow_file_range(CVE-2024-46733)

    Squashfs: sanity check symbolic link size(CVE-2024-46744)

    Input: MT - limit max slots(CVE-2024-45008)

    drm/amd/display: Assign linear_pitch_alignment even for VM(CVE-2024-46732)

    netem: fix return value if duplicate enqueue fails(CVE-2024-45016)

    sch/ netem: fix use after free in netem_dequeue(CVE-2024-46800)

    userfaultfd: fix checks for huge PMDs(CVE-2024-46787)

    netfilter: flowtable: initialise extack before use(CVE-2024-45018)

    rtnetlink: fix error logic of IFLA_BRIDGE_FLAGS writing back(CVE-2024-27414)

    xsk: validate user input for XDP_{UMEM|COMPLETION}_FILL_RING(CVE-2024-35976)

    net: atlantic: eliminate double free in error handling logic(CVE-2023-52664)

    netfilter: nf_tables: Fix potential data-race in __nft_flowtable_type_get()(CVE-2024-35898)

    net/ipv6: avoid possible UAF in ip6_route_mpath_notify()(CVE-2024-26852)

    udf: Avoid excessive partition lengths(CVE-2024-46777)

    scsi: aacraid: Fix double-free on probe failure(CVE-2024-46673)

    In the Linux kernel, the following vulnerability has been resolved:memcg_write_event_control(): fix a     user-triggerable oops  we are *not* guaranteed that anything past the terminating NUL is mapped (let alone     initialized with anything sane).(CVE-2024-45021)

    drm/client: fix null pointer dereference in drm_client_modeset_probe(CVE-2024-43894)

    drm/qxl: Add check for drm_cvt_mode(CVE-2024-43829)

    rtnetlink: Correct nested IFLA_VF_VLAN_LIST attribute validation(CVE-2024-36017)

    net: core: reject skb_copy(_expand) for fraglist GSO skbs(CVE-2024-36929)

    perf/aux: Fix AUX buffer serialization(CVE-2024-46713)

    fix bitmap corruption on close_range() with CLOSE_RANGE_UNSHARE(CVE-2024-45025)

    driver core: Fix uevent_show() vs driver detach race(CVE-2024-44952)

    x86/mtrr: Check if fixed MTRRs exist before saving them(CVE-2024-44948)

    bonding: fix null pointer deref in bond_ipsec_offload_ok(CVE-2024-44990)

    net: hns3: fix a deadlock problem when config TC during resetting(CVE-2024-44995)

    bonding: fix xfrm real_dev null pointer dereference(CVE-2024-44989)

    scsi: qla2xxx: Fix for possible memory corruption(CVE-2024-42288)

    xhci: Fix Panther point NULL pointer deref at full-speed re-enumeration(CVE-2024-45006)

    dmaengine: idxd: Prevent use after free on completion memory(CVE-2022-48867)

    drm/vmwgfx: Remove rcu locks from user resources(CVE-2022-48887)

    RDMA/hns: Fix soft lockup under heavy CEQE load(CVE-2024-43872)

    ipv6: prevent UAF in ip6_send_skb()(CVE-2024-44987)

    md/raid5: avoid BUG_ON() while continue reshape after reassembling(CVE-2024-43914)

    kvm: s390: Reject memory region operations for ucontrol VMs(CVE-2024-43819)

    ipv6: fix possible UAF in ip6_finish_output2()(CVE-2024-44986)

    devres: Fix memory leakage caused by driver API devm_free_percpu()(CVE-2024-43871)

    drm/vmwgfx: Fix a deadlock in dma buf fence polling(CVE-2024-43863)

    media: xc2028: avoid use-after-free in load_firmware_cb()(CVE-2024-43900)

    gpio: prevent potential speculation leaks in gpio_device_get_desc()(CVE-2024-44931)

    netns: Make get_net_ns() handle zero refcount net(CVE-2024-40958)

    tty: n_gsm: require CAP_NET_ADMIN to attach N_GSM0710 ldisc(CVE-2023-52880)

    memcg: protect concurrent access to mem_cgroup_idr(CVE-2024-43892)

    netfilter: ctnetlink: use helper function to calculate expect ID(CVE-2024-44944)

    udf: Fix bogus checksum computation in udf_rename()(CVE-2024-43845)

    scsi: qla2xxx: validate nvme_local_port correctly(CVE-2024-42286)

    padata: Fix possible divide-by-0 panic in padata_mt_helper()(CVE-2024-43889)

    serial: core: check uartclk for zero to avoid divide by zero(CVE-2024-43893)

    sctp: Fix null-ptr-deref in reuseport_add_sock()(CVE-2024-44935)

    scsi: qla2xxx: Complete command early within lock(CVE-2024-42287)

    net: bridge: mcast: wait for previous gc cycles when removing port(CVE-2024-44934)

    bpf: Add schedule points in batch ops(CVE-2022-48939)

    apparmor: Fix null pointer deref when receiving skb during sock creation(CVE-2023-52889)

    dev/parport: fix the array out-of-bounds risk(CVE-2024-42301)

    block: initialize integrity buffer to zero before writing it to media(CVE-2024-43854)

    dma: fix call order in dmam_free_coherent(CVE-2024-43856)

    tracing: Fix overflow in get_free_elt()(CVE-2024-43890)

    ipv6: prevent possible NULL deref in fib6_nh_init()(CVE-2024-40961)

    sysctl: always initialize i_uid/i_gid(CVE-2024-42312)

    kobject_uevent: Fix OOB access within zap_modalias_env()(CVE-2024-42292)

    A flaw was found in the Linux kernel's NVMe driver. This issue may allow an unauthenticated malicious     actor to send a set of crafted TCP packages when using NVMe over TCP, leading the NVMe driver to a NULL     pointer dereference in the NVMe driver and causing kernel panic and a denial of service.(CVE-2023-6356)

    A flaw was found in the Linux kernel's NVMe driver. This issue may allow an unauthenticated malicious     actor to send a set of crafted TCP packages when using NVMe over TCP, leading the NVMe driver to a NULL     pointer dereference in the NVMe driver, causing kernel panic and a denial of service.(CVE-2023-6535)

Tenable has extracted the preceding description block directly from the EulerOS kernel security advisory.

Note that Nessus has not tested for these issues but has instead relied only on the application's self-reported version number.

ID	Name	Product	Family	Severity
212625	EulerOS 2.0 SP12 : kernel (EulerOS-SA-2024-2953)	Nessus	Huawei Local Security Checks	high
212622	EulerOS 2.0 SP12 : kernel (EulerOS-SA-2024-2938)	Nessus	Huawei Local Security Checks	high

Detections

Analytics

CVE-2024-46733

medium

Tenable Plugins

high

high