{"vulnerability": "CVE-2022-48922", "sightings": [{"uuid": "27c6a5d1-1510-4863-a7d6-34f03605180b", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "2a075640-a300-48a4-bb44-bc6130783b9b", "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"}]}