https://vulnerability.circl.lu/sightings/feed 2026-05-04T09:47:56.856202+00:00 Vulnerability-Lookup info@circl.lu python-feedgen Contains only the most 10 recent sightings. https://vulnerability.circl.lu/sighting/3a351292-9693-4def-8f35-2f8cfe6d074f/export 2026-05-04T09:47:57.159851+00:00 Automation user http://vulnerability.circl.lu/user/automation {"uuid": "3a351292-9693-4def-8f35-2f8cfe6d074f", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2022-4892", "type": "seen", "source": "https://t.me/cibsecurity/56708", "content": "\u203c CVE-2022-4892 \u203c\n\nA vulnerability was found in MyCMS. It has been classified as problematic. This affects the function build_view of the file lib/gener/view.php of the component Visitors Module. The manipulation of the argument original/converted leads to cross site scripting. It is possible to initiate the attack remotely. The name of the patch is d64fcba4882a50e21cdbec3eb4a080cb694d26ee. It is recommended to apply a patch to fix this issue. The associated identifier of this vulnerability is VDB-218895.\n\n\ud83d\udcd6 Read\n\nvia \"National Vulnerability Database\".", "creation_timestamp": "2023-01-19T12:21:39.000000Z"} 2023-01-19T12:21:39+00:00 https://vulnerability.circl.lu/sighting/27c6a5d1-1510-4863-a7d6-34f03605180b/export 2026-05-04T09:47:57.159760+00:00 Automation user http://vulnerability.circl.lu/user/automation {"uuid": "27c6a5d1-1510-4863-a7d6-34f03605180b", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2022-48922", "type": "seen", "source": "https://t.me/cvedetector/3849", "content": "{\n \"Source\": \"CVE FEED\",\n \"Title\": \"CVE-2022-48922 - QEMU RISC-V Linux Kernel Null Pointer Dereference\", \n \"Content\": \"CVE ID : CVE-2022-48922 \nPublished : Aug. 22, 2024, 2:15 a.m. | 37\u00a0minutes ago \nDescription : In the Linux kernel, the following vulnerability has been resolved: \n \nriscv: fix oops caused by irqsoff latency tracer \n \nThe trace_hardirqs_{on,off}() require the caller to setup frame pointer \nproperly. This because these two functions use macro 'CALLER_ADDR1' (aka. \n__builtin_return_address(1)) to acquire caller info. If the $fp is used \nfor other purpose, the code generated this macro (as below) could trigger \nmemory access fault. \n \n 0xffffffff8011510e : ld a1,-16(s0) \n 0xffffffff80115112 : ld s2,-8(a1) # ] restore_all+0x12/0x6e \n \nThis because the $fp(aka. $s0) register is not used as frame pointer in the \nassembly entry code. \n \n resume_kernel: \n REG_L s0, TASK_TI_PREEMPT_COUNT(tp) \n bnez s0, restore_all \n REG_L s0, TASK_TI_FLAGS(tp) \n andi s0, s0, _TIF_NEED_RESCHED \n beqz s0, restore_all \n call preempt_schedule_irq \n j restore_all \n \nTo fix above issue, here we add one extra level wrapper for function \ntrace_hardirqs_{on,off}() so they can be safely called by low level entry \ncode. \nSeverity: 0.0 | NA \nVisit the link for more details, such as CVSS details, affected products, timeline, and more...\",\n \"Detection Date\": \"22 Aug 2024\",\n \"Type\": \"Vulnerability\"\n}\n\ud83d\udd39 t.me/cvedetector \ud83d\udd39", "creation_timestamp": "2024-08-22T05:07:49.000000Z"} 2024-08-22T05:07:49+00:00 https://vulnerability.circl.lu/sighting/f3df837e-5cf1-4b47-bf2e-c4ea588f495d/export 2026-05-04T09:47:57.159671+00:00 Automation user http://vulnerability.circl.lu/user/automation {"uuid": "f3df837e-5cf1-4b47-bf2e-c4ea588f495d", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2022-48924", "type": "seen", "source": "https://t.me/cvedetector/3850", "content": "{\n \"Source\": \"CVE FEED\",\n \"Title\": \"CVE-2022-48924 - Intel int3400_thermal Memory Leak Vulnerability\", \n \"Content\": \"CVE ID : CVE-2022-48924 \nPublished : Aug. 22, 2024, 2:15 a.m. | 37\u00a0minutes ago \nDescription : In the Linux kernel, the following vulnerability has been resolved: \n \nthermal: int340x: fix memory leak in int3400_notify() \n \nIt is easy to hit the below memory leaks in my TigerLake platform: \n \nunreferenced object 0xffff927c8b91dbc0 (size 32): \n comm \"kworker/0:2\", pid 112, jiffies 4294893323 (age 83.604s) \n hex dump (first 32 bytes): \n 4e 41 4d 45 3d 49 4e 54 33 34 30 30 20 54 68 65 NAME=INT3400 The \n 72 6d 61 6c 00 6b 6b 6b 6b 6b 6b 6b 6b 6b 6b a5 rmal.kkkkkkkkkk. \n backtrace: \n [] __kmalloc_track_caller+0x2fe/0x4a0 \n [] kvasprintf+0x65/0xd0 \n [] kasprintf+0x4e/0x70 \n [] int3400_notify+0x82/0x120 [int3400_thermal] \n [] acpi_ev_notify_dispatch+0x54/0x71 \n [] acpi_os_execute_deferred+0x17/0x30 \n [] process_one_work+0x21a/0x3f0 \n [] worker_thread+0x4a/0x3b0 \n [] kthread+0xfd/0x130 \n [] ret_from_fork+0x1f/0x30 \n \nFix it by calling kfree() accordingly. \nSeverity: 0.0 | NA \nVisit the link for more details, such as CVSS details, affected products, timeline, and more...\",\n \"Detection Date\": \"22 Aug 2024\",\n \"Type\": \"Vulnerability\"\n}\n\ud83d\udd39 t.me/cvedetector \ud83d\udd39", "creation_timestamp": "2024-08-22T05:07:50.000000Z"} 2024-08-22T05:07:50+00:00 https://vulnerability.circl.lu/sighting/acaa73cb-0fc9-43c0-910a-6f76b94db527/export 2026-05-04T09:47:57.159568+00:00 Automation user http://vulnerability.circl.lu/user/automation {"uuid": "acaa73cb-0fc9-43c0-910a-6f76b94db527", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2022-48925", "type": "seen", "source": "https://t.me/cvedetector/3851", "content": "{\n \"Source\": \"CVE FEED\",\n \"Title\": \"CVE-2022-48925 - Iberr Corrupts Global State in RDMA/cma\", \n \"Content\": \"CVE ID : CVE-2022-48925 \nPublished : Aug. 22, 2024, 2:15 a.m. | 37\u00a0minutes ago \nDescription : In the Linux kernel, the following vulnerability has been resolved: \n \nRDMA/cma: Do not change route.addr.src_addr outside state checks \n \nIf the state is not idle then resolve_prepare_src() should immediately \nfail and no change to global state should happen. However, it \nunconditionally overwrites the src_addr trying to build a temporary any \naddress. \n \nFor instance if the state is already RDMA_CM_LISTEN then this will corrupt \nthe src_addr and would cause the test in cma_cancel_operation(): \n \n if (cma_any_addr(cma_src_addr(id_priv)) && !id_priv->cma_dev) \n \nWhich would manifest as this trace from syzkaller: \n \n BUG: KASAN: use-after-free in __list_add_valid+0x93/0xa0 lib/list_debug.c:26 \n Read of size 8 at addr ffff8881546491e0 by task syz-executor.1/32204 \n \n CPU: 1 PID: 32204 Comm: syz-executor.1 Not tainted 5.12.0-rc8-syzkaller #0 \n Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 01/01/2011 \n Call Trace: \n __dump_stack lib/dump_stack.c:79 [inline] \n dump_stack+0x141/0x1d7 lib/dump_stack.c:120 \n print_address_description.constprop.0.cold+0x5b/0x2f8 mm/kasan/report.c:232 \n __kasan_report mm/kasan/report.c:399 [inline] \n kasan_report.cold+0x7c/0xd8 mm/kasan/report.c:416 \n __list_add_valid+0x93/0xa0 lib/list_debug.c:26 \n __list_add include/linux/list.h:67 [inline] \n list_add_tail include/linux/list.h:100 [inline] \n cma_listen_on_all drivers/infiniband/core/cma.c:2557 [inline] \n rdma_listen+0x787/0xe00 drivers/infiniband/core/cma.c:3751 \n ucma_listen+0x16a/0x210 drivers/infiniband/core/ucma.c:1102 \n ucma_write+0x259/0x350 drivers/infiniband/core/ucma.c:1732 \n vfs_write+0x28e/0xa30 fs/read_write.c:603 \n ksys_write+0x1ee/0x250 fs/read_write.c:658 \n do_syscall_64+0x2d/0x70 arch/x86/entry/common.c:46 \n entry_SYSCALL_64_after_hwframe+0x44/0xae \n \nThis is indicating that an rdma_id_private was destroyed without doing \ncma_cancel_listens(). \n \nInstead of trying to re-use the src_addr memory to indirectly create an \nany address derived from the dst build one explicitly on the stack and \nbind to that as any other normal flow would do. rdma_bind_addr() will copy \nit over the src_addr once it knows the state is valid. \n \nThis is similar to commit bc0bdc5afaa7 (\"RDMA/cma: Do not change \nroute.addr.src_addr.ss_family\") \nSeverity: 0.0 | NA \nVisit the link for more details, such as CVSS details, affected products, timeline, and more...\",\n \"Detection Date\": \"22 Aug 2024\",\n \"Type\": \"Vulnerability\"\n}\n\ud83d\udd39 t.me/cvedetector \ud83d\udd39", "creation_timestamp": "2024-08-22T05:07:51.000000Z"} 2024-08-22T05:07:51+00:00 https://vulnerability.circl.lu/sighting/c1455dcf-983e-4603-a22e-b2551ebdfbac/export 2026-05-04T09:47:57.159459+00:00 Automation user http://vulnerability.circl.lu/user/automation {"uuid": "c1455dcf-983e-4603-a22e-b2551ebdfbac", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2022-48923", "type": "seen", "source": "https://t.me/cvedetector/3852", "content": "{\n \"Source\": \"CVE FEED\",\n \"Title\": \"CVE-2022-48923 - Btrfs LZO Decompression Off-Path Information Disclosure\", \n \"Content\": \"CVE ID : CVE-2022-48923 \nPublished : Aug. 22, 2024, 2:15 a.m. | 37\u00a0minutes ago \nDescription : In the Linux kernel, the following vulnerability has been resolved: \n \nbtrfs: prevent copying too big compressed lzo segment \n \nCompressed length can be corrupted to be a lot larger than memory \nwe have allocated for buffer. \nThis will cause memcpy in copy_compressed_segment to write outside \nof allocated memory. \n \nThis mostly results in stuck read syscall but sometimes when using \nbtrfs send can get #GP \n \n kernel: general protection fault, probably for non-canonical address 0x841551d5c1000: 0000 [#1] PREEMPT SMP NOPTI \n kernel: CPU: 17 PID: 264 Comm: kworker/u256:7 Tainted: P OE 5.17.0-rc2-1 #12 \n kernel: Workqueue: btrfs-endio btrfs_work_helper [btrfs] \n kernel: RIP: 0010:lzo_decompress_bio (./include/linux/fortify-string.h:225 fs/btrfs/lzo.c:322 fs/btrfs/lzo.c:394) btrfs \n Code starting with the faulting instruction \n =========================================== \n 0:* 48 8b 06 mov (%rsi),%rax \n kernel: end_compressed_bio_read (fs/btrfs/compression.c:104 fs/btrfs/compression.c:1363 fs/btrfs/compression.c:323) btrfs \n kernel: end_workqueue_fn (fs/btrfs/disk-io.c:1923) btrfs \n kernel: btrfs_work_helper (fs/btrfs/async-thread.c:326) btrfs \n kernel: process_one_work (./arch/x86/include/asm/jump_label.h:27 ./include/linux/jump_label.h:212 ./include/trace/events/workqueue.h:108 kernel/workqueue.c:2312) \n kernel: worker_thread (./include/linux/list.h:292 kernel/workqueue.c:2455) \n kernel: ? process_one_work (kernel/workqueue.c:2397) \n kernel: kthread (kernel/kthread.c:377) \n kernel: ? kthread_complete_and_exit (kernel/kthread.c:332) \n kernel: ret_from_fork (arch/x86/entry/entry_64.S:301) \n kernel: \nSeverity: 0.0 | NA \nVisit the link for more details, such as CVSS details, affected products, timeline, and more...\",\n \"Detection Date\": \"22 Aug 2024\",\n \"Type\": \"Vulnerability\"\n}\n\ud83d\udd39 t.me/cvedetector \ud83d\udd39", "creation_timestamp": "2024-08-22T05:07:52.000000Z"} 2024-08-22T05:07:52+00:00 https://vulnerability.circl.lu/sighting/40dcbacf-1d3b-4cda-b710-a6335eee9055/export 2026-05-04T09:47:57.159359+00:00 Automation user http://vulnerability.circl.lu/user/automation {"uuid": "40dcbacf-1d3b-4cda-b710-a6335eee9055", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2022-48921", "type": "seen", "source": "https://t.me/cvedetector/3853", "content": "{\n \"Source\": \"CVE FEED\",\n \"Title\": \"CVE-2022-48921 - Linux Kernel Sched/Fair Null Pointer Dereference Vulnerability in Red Hat Enterprise Linux\", \n \"Content\": \"CVE ID : CVE-2022-48921 \nPublished : Aug. 22, 2024, 2:15 a.m. | 37\u00a0minutes ago \nDescription : In the Linux kernel, the following vulnerability has been resolved: \n \nsched/fair: Fix fault in reweight_entity \n \nSyzbot found a GPF in reweight_entity. This has been bisected to \ncommit 4ef0c5c6b5ba (\"kernel/sched: Fix sched_fork() access an invalid \nsched_task_group\") \n \nThere\u00a0is a race between sched_post_fork() and setpriority(PRIO_PGRP) \nwithin a thread group that causes a null-ptr-deref\u00a0in \nreweight_entity() in CFS. The scenario is that the main process spawns \nnumber of new threads, which then call setpriority(PRIO_PGRP, 0, -20), \nwait, and exit. For each of the new threads the copy_process() gets \ninvoked, which adds the new task_struct and calls sched_post_fork() \nfor it. \n \nIn the above scenario there is a possibility that \nsetpriority(PRIO_PGRP) and set_one_prio() will be called for a thread \nin the group that is just being created by copy_process(), and for \nwhich the sched_post_fork() has not been executed yet. This will \ntrigger a null pointer dereference in reweight_entity(),\u00a0as it will \ntry to access the run queue pointer, which hasn't been set. \n \nBefore the mentioned change the cfs_rq pointer for the task has been \nset in sched_fork(), which is called much earlier in copy_process(), \nbefore the new task is added to the thread_group. Now it is done in \nthe sched_post_fork(), which is called after that. To fix the issue \nthe remove the update_load param from the update_load param() function \nand call reweight_task() only if the task flag doesn't have the \nTASK_NEW flag set. \nSeverity: 0.0 | NA \nVisit the link for more details, such as CVSS details, affected products, timeline, and more...\",\n \"Detection Date\": \"22 Aug 2024\",\n \"Type\": \"Vulnerability\"\n}\n\ud83d\udd39 t.me/cvedetector \ud83d\udd39", "creation_timestamp": "2024-08-22T05:07:52.000000Z"} 2024-08-22T05:07:52+00:00 https://vulnerability.circl.lu/sighting/7c91ccc9-85f7-4145-8ff7-c2ade979c889/export 2026-05-04T09:47:57.159227+00:00 Automation user http://vulnerability.circl.lu/user/automation {"uuid": "7c91ccc9-85f7-4145-8ff7-c2ade979c889", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2022-48920", "type": "seen", "source": "https://t.me/cvedetector/3854", "content": "{\n \"Source\": \"CVE FEED\",\n \"Title\": \"CVE-2022-48920 - Btrfs flushoncommit warning vulnerability\", \n \"Content\": \"CVE ID : CVE-2022-48920 \nPublished : Aug. 22, 2024, 2:15 a.m. | 37\u00a0minutes ago \nDescription : In the Linux kernel, the following vulnerability has been resolved: \n \nbtrfs: get rid of warning on transaction commit when using flushoncommit \n \nWhen using the flushoncommit mount option, during almost every transaction \ncommit we trigger a warning from __writeback_inodes_sb_nr(): \n \n $ cat fs/fs-writeback.c: \n (...) \n static void __writeback_inodes_sb_nr(struct super_block *sb, ... \n { \n (...) \n WARN_ON(!rwsem_is_locked(&sb->s_umount)); \n (...) \n } \n (...) \n \nThe trace produced in dmesg looks like the following: \n \n [947.473890] WARNING: CPU: 5 PID: 930 at fs/fs-writeback.c:2610 __writeback_inodes_sb_nr+0x7e/0xb3 \n [947.481623] Modules linked in: nfsd nls_cp437 cifs asn1_decoder cifs_arc4 fscache cifs_md4 ipmi_ssif \n [947.489571] CPU: 5 PID: 930 Comm: btrfs-transacti Not tainted 95.16.3-srb-asrock-00001-g36437ad63879 #186 \n [947.497969] RIP: 0010:__writeback_inodes_sb_nr+0x7e/0xb3 \n [947.502097] Code: 24 10 4c 89 44 24 18 c6 (...) \n [947.519760] RSP: 0018:ffffc90000777e10 EFLAGS: 00010246 \n [947.523818] RAX: 0000000000000000 RBX: 0000000000963300 RCX: 0000000000000000 \n [947.529765] RDX: 0000000000000000 RSI: 000000000000fa51 RDI: ffffc90000777e50 \n [947.535740] RBP: ffff888101628a90 R08: ffff888100955800 R09: ffff888100956000 \n [947.541701] R10: 0000000000000002 R11: 0000000000000001 R12: ffff888100963488 \n [947.547645] R13: ffff888100963000 R14: ffff888112fb7200 R15: ffff888100963460 \n [947.553621] FS: 0000000000000000(0000) GS:ffff88841fd40000(0000) knlGS:0000000000000000 \n [947.560537] CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033 \n [947.565122] CR2: 0000000008be50c4 CR3: 000000000220c000 CR4: 00000000001006e0 \n [947.571072] Call Trace: \n [947.572354] \n [947.573266] btrfs_commit_transaction+0x1f1/0x998 \n [947.576785] ? start_transaction+0x3ab/0x44e \n [947.579867] ? schedule_timeout+0x8a/0xdd \n [947.582716] transaction_kthread+0xe9/0x156 \n [947.585721] ? btrfs_cleanup_transaction.isra.0+0x407/0x407 \n [947.590104] kthread+0x131/0x139 \n [947.592168] ? set_kthread_struct+0x32/0x32 \n [947.595174] ret_from_fork+0x22/0x30 \n [947.597561] \n [947.598553] ---[ end trace 644721052755541c ]--- \n \nThis is because we started using writeback_inodes_sb() to flush delalloc \nwhen committing a transaction (when using -o flushoncommit), in order to \navoid deadlocks with filesystem freeze operations. This change was made \nby commit ce8ea7cc6eb313 (\"btrfs: don't call btrfs_start_delalloc_roots \nin flushoncommit\"). After that change we started producing that warning, \nand every now and then a user reports this since the warning happens too \noften, it spams dmesg/syslog, and a user is unsure if this reflects any \nproblem that might compromise the filesystem's reliability. \n \nWe can not just lock the sb->s_umount semaphore before calling \nwriteback_inodes_sb(), because that would at least deadlock with \nfilesystem freezing, since at fs/super.c:freeze_super() sync_filesystem() \nis called while we are holding that semaphore in write mode, and that can \ntrigger a transaction commit, resulting in a deadlock. It would also \ntrigger the same type of deadlock in the unmount path. Possibly, it could \nalso introduce some other locking dependencies that lockdep would report. \n \nTo fix this call try_to_writeback_inodes_sb() instead of \nwriteback_inodes_sb(), because that will try to read lock sb->s_umount \nand then will only call writeback_inodes_sb() if it was able to lock it. \nThis is fine because the cases where it can't read lock sb->s_umount \nare during a filesystem unmount or during a filesystem freeze - in those \ncases sb->s_umount is write locked and sync_filesystem() is called, which \ncalls writeback_inodes_sb(). In other words, in all cases where we can[...]", "creation_timestamp": "2024-08-22T05:07:54.000000Z"} 2024-08-22T05:07:54+00:00 https://vulnerability.circl.lu/sighting/7a7c695b-d8c9-4f4f-8513-9a370fb4e2bc/export 2026-05-04T09:47:57.158465+00:00 Automation user http://vulnerability.circl.lu/user/automation {"uuid": "7a7c695b-d8c9-4f4f-8513-9a370fb4e2bc", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2022-48923", "type": "published-proof-of-concept", "source": "https://t.me/DarkWebInformer_CVEAlerts/16473", "content": "\ud83d\udd17 DarkWebInformer.com - Cyber Threat Intelligence\n\ud83d\udccc CVE ID: CVE-2022-48923\n\ud83d\udd25 CVSS Score: N/A\n\ud83d\udd39 Description: In the Linux kernel, the following vulnerability has been resolved:\n\nbtrfs: prevent copying too big compressed lzo segment\n\nCompressed length can be corrupted to be a lot larger than memory\nwe have allocated for buffer.\nThis will cause memcpy in copy_compressed_segment to write outside\nof allocated memory.\n\nThis mostly results in stuck read syscall but sometimes when using\nbtrfs send can get #GP\n\n kernel: general protection fault, probably for non-canonical address 0x841551d5c1000: 0000 [#1] PREEMPT SMP NOPTI\n kernel: CPU: 17 PID: 264 Comm: kworker/u256:7 Tainted: P OE 5.17.0-rc2-1 #12\n kernel: Workqueue: btrfs-endio btrfs_work_helper [btrfs]\n kernel: RIP: 0010:lzo_decompress_bio (./include/linux/fortify-string.h:225 fs/btrfs/lzo.c:322 fs/btrfs/lzo.c:394) btrfs\n Code starting with the faulting instruction\n ===========================================\n 0:* 48 8b 06 mov (%rsi),%rax <-- trapping instruction\n 3: 48 8d 79 08 lea 0x8(%rcx),%rdi\n 7: 48 83 e7 f8 and $0xfffffffffffffff8,%rdi\n b: 48 89 01 mov %rax,(%rcx)\n e: 44 89 f0 mov %r14d,%eax\n 11: 48 8b 54 06 f8 mov -0x8(%rsi,%rax,1),%rdx\n kernel: RSP: 0018:ffffb110812efd50 EFLAGS: 00010212\n kernel: RAX: 0000000000001000 RBX: 000000009ca264c8 RCX: ffff98996e6d8ff8\n kernel: RDX: 0000000000000064 RSI: 000841551d5c1000 RDI: ffffffff9500435d\n kernel: RBP: ffff989a3be856c0 R08: 0000000000000000 R09: 0000000000000000\n kernel: R10: 0000000000000000 R11: 0000000000001000 R12: ffff98996e6d8000\n kernel: R13: 0000000000000008 R14: 0000000000001000 R15: 000841551d5c1000\n kernel: FS: 0000000000000000(0000) GS:ffff98a09d640000(0000) knlGS:0000000000000000\n kernel: CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033\n kernel: CR2: 00001e9f984d9ea8 CR3: 000000014971a000 CR4: 00000000003506e0\n kernel: Call Trace:\n kernel: \n kernel: end_compressed_bio_read (fs/btrfs/compression.c:104 fs/btrfs/compression.c:1363 fs/btrfs/compression.c:323) btrfs\n kernel: end_workqueue_fn (fs/btrfs/disk-io.c:1923) btrfs\n kernel: btrfs_work_helper (fs/btrfs/async-thread.c:326) btrfs\n kernel: process_one_work (./arch/x86/include/asm/jump_label.h:27 ./include/linux/jump_label.h:212 ./include/trace/events/workqueue.h:108 kernel/workqueue.c:2312)\n kernel: worker_thread (./include/linux/list.h:292 kernel/workqueue.c:2455)\n kernel: ? process_one_work (kernel/workqueue.c:2397)\n kernel: kthread (kernel/kthread.c:377)\n kernel: ? kthread_complete_and_exit (kernel/kthread.c:332)\n kernel: ret_from_fork (arch/x86/entry/entry_64.S:301)\n kernel: \n\ud83d\udccf Published: 2024-08-22T01:32:58.084Z\n\ud83d\udccf Modified: 2025-05-15T12:28:19.161Z\n\ud83d\udd17 References:\n1. https://git.kernel.org/stable/c/8df508b7a44cd8110c726057cd28e8f8116885eb\n2. https://git.kernel.org/stable/c/e326bd06cdde46df952361456232022298281d16\n3. https://git.kernel.org/stable/c/741b23a970a79d5d3a1db2d64fa2c7b375a4febb", "creation_timestamp": "2025-05-15T12:34:19.000000Z"} 2025-05-15T12:34:19+00:00 https://vulnerability.circl.lu/sighting/92efdda2-d4d8-4d1f-aed6-73d99386c745/export 2026-05-04T09:47:57.157643+00:00 Alexandre Dulaunoy http://vulnerability.circl.lu/user/adulau {"uuid": "92efdda2-d4d8-4d1f-aed6-73d99386c745", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "c933734a-9be8-4142-889e-26e95c752803", "vulnerability": "CVE-2022-48920", "type": "seen", "source": "https://vulnerability.circl.lu/bundle/816dcc8e-f25a-4895-9b59-1bbd9caeccb8", "content": "", "creation_timestamp": "2025-12-03T14:14:49.267740Z"} 2025-12-03T14:14:49.267740+00:00 https://vulnerability.circl.lu/sighting/14866892-7a0c-4112-8e22-fe312123c463/export 2026-05-04T09:47:57.154598+00:00 Joseph Lee http://vulnerability.circl.lu/user/syspect {"uuid": "14866892-7a0c-4112-8e22-fe312123c463", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "86ecb4e1-bb32-44d5-9f39-8a4673af8385", "vulnerability": "CVE-2022-48929", "type": "seen", "source": "https://www.cert.ssi.gouv.fr/avis/CERTFR-2026-AVI-0316/", "content": "", "creation_timestamp": "2026-03-19T00:00:00.000000Z"} 2026-03-19T00:00:00+00:00