deardaniel/secdata-raw huggingface dataset:
CVE: CVE-2025-64760
Published: 2025-12-08
Description: Tuleap is a free and open source suite for management of software development and collaboration. Versions of Tuleap Community Edition prior to 17.0.99[PII_REDACTED] and Tuleap Enterprise Edition prior to 17.0-3 and 16.13-8 have missing CSRF protections which allow attackers to create or remove tracker triggers. This issue is fixed in Tuleap Community Edition version 17.0.99[PII_REDACTED] and Tuleap Enterprise Edition versions 17.0-3 and 16.13-8.
CVSS Score: 4.6 (MEDIUM)
CWE: CWE-352
References: https://github.com/Enalean/tuleap/commit/71d427b0f7ed8fa269a5ee6f7a557cf3dfc99cd4; https://github.com/Enalean/tuleap/security/advisories/GHSA-f2xv-x3g6-4j9p; https://tuleap.net/plugins/git/tuleap/tuleap/stable?a=commit&h=71d427b0f7ed8fa269a5ee6f7a557cf3dfc99cd4
CVE: CVE-2025-65962
Published: 2025-12-09
Description: Tuleap is a free and open source suite for management of software development and collaboration. Versions of Tuleap Community Edition prior to 17.0.99[PII_REDACTED] and Tuleap Enterprise Edition versions prior to 17.0-4 and 16.13-9 are mission CSRF protections in its tracker field dependencies, allowing attackers to modify tracker fields. This issue is fixed in Tuleap Community Edition version 17.0.99[PII_REDACTED] and Tuleap Enterprise Edition versions 17.0-4 and 16.13-9.
CVSS Score: 4.6 (MEDIUM)
CWE: CWE-352
References: https://github.com/Enalean/tuleap/commit/26678c5b411042e68964b199bf88a[PII_REDACTED]3; https://github.com/Enalean/tuleap/security/advisories/GHSA-9hgc-cm68-rrgc; https://tuleap.net/plugins/git/tuleap/tuleap/stable?a=commit&h=26678c5b411042e68964b199bf88a[PII_REDACTED]3
CVE: CVE-2025-65964
Published: 2025-12-09
Description: n8n is an open source workflow automation platform. Versions 0.123.1 through 1.119.1 do not have adequate protections to prevent RCE through the project's pre-commit hooks. The Add Config operation allows workflows to set arbitrary Git configuration values, including core.hooksPath, which can point to a malicious Git hook that executes arbitrary commands on the n8n host during subsequent Git operations. Exploitation requires the ability to create or modify an n8n workflow using the Git node. This issue is fixed in version 1.119.2. Workarounds include excluding the Git Node (Docs) and avoiding cloning or interacting with untrusted repositories using the Git Node.
CVSS Score: 8.8 (HIGH)
CWE: CWE-829
References: https://github.com/n8n-io/n8n/commit/d5a1171f95f75def5c3ac577707ab913e22aef04; https://github.com/n8n-io/n8n/releases/tag/n8n%401.119.2; https://github.com/n8n-io/n8n/security/advisories/GHSA-wpqc-h9wp-chmq
CVE: CVE-2025-66202
Published: 2025-12-09
Description: Astro is a web framework. Versions 5.15.7 and below have a double URL encoding bypass which allows any unauthenticated attacker to bypass path-based authentication checks in Astro middleware, granting unauthorized access to protected routes. While the original CVE-2025-64765 was fixed in v5.15.8, the fix is insufficient as it only decodes once. By using double-encoded URLs, attackers can still bypass authentication and access any route protected by middleware pathname checks. This issue is fixed in version 5.15.8.
CVSS Score: 6.5 (MEDIUM)
CWE: CWE-647
References: https://github.com/withastro/astro/commit/6f800813516b07bbe12c666a92937525fddb58ce; https://github.com/withastro/astro/security/advisories/GHSA-ggxq-hp9w-j794; https://github.com/withastro/astro/security/advisories/GHSA-whqg-ppgf-wp8c
CVE: CVE-2025-66204
Published: 2025-12-09
Description: WBCE CMS is a content management system. Version 1.6.4 contains a brute-force protection bypass where an attacker can indefinitely reset the counter by modifying `X-Forwarded-For` on each request, gaining unlimited password guessing attempts, effectively bypassing all brute-force protection. The application fully trusts the `X-Forwarded-For` header without validating it or restricting its usage. This issue is fixed in version 1.6.5.
CVSS Score: 8.1 (HIGH)
CWE: CWE-307, CWE-693, CWE-307
References: https://github.com/WBCE/WBCE_CMS/commit/3765baddf27f31bbbea9c0228c452268621b25e5; https://github.com/WBCE/WBCE_CMS/releases/tag/1.6.5; https://github.com/WBCE/WBCE_CMS/security/advisories/GHSA-f676-f375-m7mw
CVE: CVE-2025-66469
Published: 2025-12-09
Description: NiceGUI is a Python-based UI framework. Versions 3.3.1 and below are vulnerable to Reflected XSS through its ui.add_css, ui.add_scss, and ui.add_sass functions. The functions lack proper sanitization or encoding for the JavaScript context they generate. An attacker can break out of the intended <style> or <script> tags by injecting closing tags (e.g., </style> or </script>), allowing for the execution of arbitrary JavaScript. This issue is fixed in version 3.4.0.
CVSS Score: 6.1 (MEDIUM)
CWE: CWE-79
References: https://github.com/zauberzeug/nicegui/commit/a8fd25b7d5e23afb1952d0f60a1940e18b5f1ca8; https://github.com/zauberzeug/nicegui/security/advisories/GHSA-72qc-wxch-74mg; https://github.com/zauberzeug/nicegui/security/advisories/GHSA-72qc-wxch-74mg
CVE: CVE-2013-10031
Published: 2025-12-09
Description: Plack-Middleware-Session versions before 0.17 may be vulnerable to HMAC comparison timing attacks
CVSS Score: 7.5 (HIGH)
CWE: CWE-1254
References: https://github.com/plack/Plack-Middleware-Session/commit/b7f0252269ba1bb812b5dc02303754fe94c808e4
CVE: CVE-2022-50631
Published: 2025-12-09
Description: In the Linux kernel, the following vulnerability has been resolved:

RISC-V: kexec: Fix memory leak of fdt buffer

This is reported by kmemleak detector:

unreferenced object 0xff[PII_REDACTED]4000 (size 9588):
  comm "kexec", pid 146, jiffies[PII_REDACTED] (age 64.788s)
  hex dump (first 32 bytes):
    d0 0d fe ed 00 00 12 ed 00 00 00 48 00 00 11 40  ...........H...@
    00 00 00 28 00 00 00 11 00 00 00 02 00 00 00 00  ...(............
  backtrace:
    [<00000000f95b17c4>] kmemleak_alloc+0x34/0x3e
    [<00000000b9ec8e3e>] kmalloc_order+0x9c/0xc4
    [<00000000a95cf02e>] kmalloc_order_trace+0x34/0xb6
    [<00000000f01e68b4>] __kmalloc+0x5c2/0x62a
    [<000000002bd497b2>] kvmalloc_node+0x66/0xd6
    [<[PII_REDACTED]6542fa>] of_kexec_alloc_and_setup_fdt+0xa6/0x6ea
    [<00000000e1166bde>] elf_kexec_load+0x206/0x4ec
    [<[PII_REDACTED]548e09>] kexec_image_load_default+0x40/0x4c
    [<[PII_REDACTED]fbe1b4>] sys_kexec_file_load+0x1c4/0x322
    [<[PII_REDACTED]c62c03>] ret_from_syscall+0x0/0x2

In elf_kexec_load(), a buffer is allocated via kvmalloc() to store fdt.
While it's not freed back to system when kexec kernel is reloaded or
unloaded.  Then memory leak is caused.  Fix it by introducing riscv
specific function arch_kimage_file_post_load_cleanup(), and freeing the
buffer there.
References: https://git.kernel.org/stable/c/96df59b1ae23f5c11698c3c2159aeb2ecd4944a4; https://git.kernel.org/stable/c/c66ad198b6497dee8f45d7ed5c03629c4525c7d0; https://git.kernel.org/stable/c/dc387c34d8dd10b02a333df098f8fd9bba177a45
CVE: CVE-2022-50632
Published: 2025-12-09
Description: In the Linux kernel, the following vulnerability has been resolved:

drivers: perf: marvell_cn10k: Fix hotplug callback leak in tad_pmu_init()

tad_pmu_init() won't remove the callback added by cpuhp_setup_state_multi()
when platform_driver_register() failed. Remove the callback by
cpuhp_remove_multi_state() in fail path.

Similar to the handling of arm_ccn_init() in commit 26242b330093 ("bus:
arm-ccn: Prevent hotplug callback leak")
References: https://git.kernel.org/stable/c/367404bfd1aa87b2a50059cd8edc6c12c367cd15; https://git.kernel.org/stable/c/7772f4de934123ccd7c7cdc1dc4e46fdd5d767fb; https://git.kernel.org/stable/c/973ae93d80d9d262f695eb485a1902b74c4b9098
CVE: CVE-2022-50633
Published: 2025-12-09
Description: In the Linux kernel, the following vulnerability has been resolved:

usb: dwc3: qcom: Fix memory leak in dwc3_qcom_interconnect_init

of_icc_get() alloc resources for path handle, we should release it when not
need anymore. Like the release in dwc3_qcom_interconnect_exit() function.
Add icc_put() in error handling to fix this.
References: https://git.kernel.org/stable/c/2f3b51189f7a7be5d822fb8c537d778c57eb9821; https://git.kernel.org/stable/c/56f6de394f0f57928cd401255a5c7866b68a77e3; https://git.kernel.org/stable/c/8c39c8d23ff9fb1beb6e16cf0ae929c764538625
CVE: CVE-2022-50634
Published: 2025-12-09
Description: In the Linux kernel, the following vulnerability has been resolved:

power: supply: cw2015: Fix potential null-ptr-deref in cw_bat_probe()

cw_bat_probe() calls create_singlethread_workqueue() and not checked the
ret value, which may return NULL. And a null-ptr-deref may happen:

cw_bat_probe()
    create_singlethread_workqueue() # failed, cw_bat->wq is NULL
    queue_delayed_work()
        queue_delayed_work_on()
            __queue_delayed_work()  # warning here, but continue
                __queue_work()      # access wq->flags, null-ptr-deref

Check the ret value and return -ENOMEM if it is NULL.
References: https://git.kernel.org/stable/c/5150b76aa2eb8bb8feb7f7a048417f9d39c3dd04; https://git.kernel.org/stable/c/97f2b4ddb0aa700d673691a7d5e44d226d22bab7; https://git.kernel.org/stable/c/f7e2ba8ed08138102f21f3fe6414498c93177fd8
CVE: CVE-2022-50635
Published: 2025-12-09
Description: In the Linux kernel, the following vulnerability has been resolved:

powerpc/kprobes: Fix null pointer reference in arch_prepare_kprobe()

I found a null pointer reference in arch_prepare_kprobe():

  # echo 'p cmdline_proc_show' > kprobe_events
  # echo 'p cmdline_proc_show+16' >> kprobe_events
  Kernel attempted to read user page (0) - exploit attempt? (uid: 0)
  BUG: Kernel NULL pointer dereference on read at 0x00000000
  Faulting instruction address: 0xc[PII_REDACTED]50bfc
  Oops: Kernel access of bad area, sig: 11 [#1]
  LE PAGE_SIZE=64K MMU=Radix SMP NR_CPUS=2048 NUMA PowerNV
  Modules linked in:
  CPU: 0 PID: 122 Comm: sh Not tainted 6.0.0-rc3-00007-gdcf8e5633e2e #10
  NIP:  c[PII_REDACTED]50bfc LR: c[PII_REDACTED]50bec CTR:[PII_REDACTED]005bdc
  REGS: c[PII_REDACTED]475b0 TRAP: 0300   Not tainted  (6.0.0-rc3-00007-gdcf8e5633e2e)
  MSR:  [PII_REDACTED] <SF,HV,EE,ME,IR,DR,RI,LE>  CR: 88002444  XER: 20040006
  CFAR: c[PII_REDACTED]2d100 DAR: [PII_REDACTED] DSISR: 40000000 IRQMASK: 0
  ...
  NIP arch_prepare_kprobe+0x10c/0x2d0
  LR  arch_prepare_kprobe+0xfc/0x2d0
  Call Trace:
    0xc[PII_REDACTED]f77a0 (unreliable)
    register_kprobe+0x3c0/0x7a0
    __register_trace_kprobe+0x140/0x1a0
    __trace_kprobe_create+0x794/0x1040
    trace_probe_create+0xc4/0xe0
    create_or_delete_trace_kprobe+0x2c/0x80
    trace_parse_run_command+0xf0/0x210
    probes_write+0x20/0x40
    vfs_write+0xfc/0x450
    ksys_write+0x84/0x140
    system_call_exception+0x17c/0x3a0
    system_call_vectored_common+0xe8/0x278
  --- interrupt: 3000 at 0x7fffa5682de0
  NIP:  00007fffa5682de0 LR: [PII_REDACTED] CTR: [PII_REDACTED]
  REGS: c[PII_REDACTED]47e80 TRAP: 3000   Not tainted  (6.0.0-rc3-00007-gdcf8e5633e2e)
  MSR: [PII_REDACTED]80f033 <SF,HV,VEC,VSX,EE,PR,FP,ME,IR,DR,RI,LE>  CR: 44002408  XER: 00000000

The address being probed has some special:

  cmdline_proc_show: Probe based on ftrace
  cmdline_proc_show+16: Probe for the next instruction at the ftrace location

The ftrace-based kprobe does not generate kprobe::ainsn::insn, it gets
set to NULL. In arch_prepare_kprobe() it will check for:

  ...
  prev = get_kprobe(p->addr - 1);
  preempt_enable_no_resched();
  if (prev && ppc_inst_prefixed(ppc_inst_read(prev->ainsn.insn))) {
  ...

If prev is based on ftrace, 'ppc_inst_read(prev->ainsn.insn)' will occur
with a null pointer reference. At this point prev->addr will not be a
prefixed instruction, so the check can be skipped.

Check if prev is ftrace-based kprobe before reading 'prev->ainsn.insn'
to fix this problem.

[mpe: Trim oops]
References: https://git.kernel.org/stable/c/4eac4f6a86ae73ef4b772d37398beeba2fbfde4e; https://git.kernel.org/stable/c/5fd1b369387c53ee6c774ab86e32e362a1e537ac; https://git.kernel.org/stable/c/7f536a8cb62dd5c084f112373fc34cdb5168a813
CVE: CVE-2022-50636
Published: 2025-12-09
Description: In the Linux kernel, the following vulnerability has been resolved:

PCI: Fix pci_device_is_present() for VFs by checking PF

pci_device_is_present() previously didn't work for VFs because it reads the
Vendor and Device ID, which are 0xffff for VFs, which looks like they
aren't present.  Check the PF instead.

Wei Gong reported that if virtio I/O is in progress when the driver is
unbound or "0" is written to /sys/.../sriov_numvfs, the virtio I/O
operation hangs, which may result in output like this:

  task:bash state:D stack:    0 pid: 1773 ppid:  1241 flags:0x00004002
  Call Trace:
   schedule+0x4f/0xc0
   blk_mq_freeze_queue_wait+0x69/0xa0
   blk_mq_freeze_queue+0x1b/0x20
   blk_cleanup_queue+0x3d/0xd0
   virtblk_remove+0x3c/0xb0 [virtio_blk]
   virtio_dev_remove+0x4b/0x80
   ...
   device_unregister+0x1b/0x60
   unregister_virtio_device+0x18/0x30
   virtio_pci_remove+0x41/0x80
   pci_device_remove+0x3e/0xb0

This happened because pci_device_is_present(VF) returned "false" in
virtio_pci_remove(), so it called virtio_break_device().  The broken vq
meant that vring_interrupt() skipped the vq.callback() that would have
completed the virtio I/O operation via virtblk_done().

[bhelgaas: commit log, simplify to always use pci_physfn(), add stable tag]
References: https://git.kernel.org/stable/c/518573988a2f14f517403db2ece5ddaefba21e94; https://git.kernel.org/stable/c/643d77fda08d06f863af35e80a7e517ea61d9629; https://git.kernel.org/stable/c/65bd0962992abd42e77a05e68c7b40e7c73726d1
CVE: CVE-2022-50637
Published: 2025-12-09
Description: In the Linux kernel, the following vulnerability has been resolved:

cpufreq: qcom-hw: Fix memory leak in qcom_cpufreq_hw_read_lut()

If "cpu_dev" fails to get opp table in qcom_cpufreq_hw_read_lut(),
the program will return, resulting in "table" resource is not released.
References: https://git.kernel.org/stable/c/242e23be8f31ebd90525c57ee3244c28e99a1697; https://git.kernel.org/stable/c/3ef12a4a8ef5553af9c3fd2719a616637a102568; https://git.kernel.org/stable/c/4ea765b10624d[PII_REDACTED]0d381c60f53593033
CVE: CVE-2022-50639
Published: 2025-12-09
Description: In the Linux kernel, the following vulnerability has been resolved:

io-wq: Fix memory leak in worker creation

If the CPU mask allocation for a node fails, then the memory allocated for
the 'io_wqe' struct of the current node doesn't get freed on the error
handling path, since it has not yet been added to the 'wqes' array.

This was spotted when fuzzing v6.1-rc1 with Syzkaller:
BUG: memory leak
unreferenced object 0xffff8880093d5000 (size 1024):
  comm "syz-executor.2", pid 7701, jiffies[PII_REDACTED] (age 13.900s)
  hex dump (first 32 bytes):
    00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00  ................
    00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00  ................
  backtrace:
    [<00000000cb463369>] __kmem_cache_alloc_node+0x18e/0x720
    [<[PII_REDACTED]7a3f9c>] kmalloc_node_trace+0x2a/0x130
    [<000000004e107011>] io_wq_create+0x7b9/0xdc0
    [<00000000c38b2018>] io_uring_alloc_task_context+0x31e/0x59d
    [<[PII_REDACTED]7399da>] __io_uring_add_tctx_node.cold+0x19/0x1ba
    [<000000007e0e7a79>] io_uring_setup.cold+0x1b80/0x1dce
    [<00000000b545e9f6>] __x64_sys_io_uring_setup+0x5d/0x80
    [<000000008a8a7508>] do_syscall_64+0x5d/0x90
    [<000000004ac08bec>] entry_SYSCALL_64_after_hwframe+0x63/0xcd
References: https://git.kernel.org/stable/c/996d3efeb091c503afd3ee6b5e20eabf446fd955; https://git.kernel.org/stable/c/b6e2c54be37d5eb4f6666e6aa59cd0581c7ffc3c; https://git.kernel.org/stable/c/ed981911a7c90a604f4a2bee908ab07e3b786aca
CVE: CVE-2022-50640
Published: 2025-12-09
Description: In the Linux kernel, the following vulnerability has been resolved:

mmc: core: Fix kernel panic when remove non-standard SDIO card

SDIO tuple is only allocated for standard SDIO card, especially it causes
memory corruption issues when the non-standard SDIO card has removed, which
is because the card device's reference counter does not increase for it at
sdio_init_func(), but all SDIO card device reference counter gets decreased
at sdio_release_func().
References: https://git.kernel.org/stable/c/1e8cd93ae536581562bab4e1d8c5315bbc2548bf; https://git.kernel.org/stable/c/1fb79478695d92bab1c120ad3dad05252b02a29d; https://git.kernel.org/stable/c/66d461a92f32b6995b630625d350259b6b1f961b
CVE: CVE-2022-50641
Published: 2025-12-09
Description: In the Linux kernel, the following vulnerability has been resolved:

HSI: omap_ssi: Fix refcount leak in ssi_probe

When returning or breaking early from a
for_each_available_child_of_node() loop, we need to explicitly call
of_node_put() on the child node to possibly release the node.
References: https://git.kernel.org/stable/c/0eff9ef67d91e350d2047c3e13b6c3b7d0c90bf4; https://git.kernel.org/stable/c/18e199a5541aad6dc5cf51bc3f712247b2d17894; https://git.kernel.org/stable/c/20fbaff6699ea5553c67550e867d6f90b7085447
CVE: CVE-2022-50642
Published: 2025-12-09
Description: In the Linux kernel, the following vulnerability has been resolved:

platform/chrome: cros_ec_typec: zero out stale pointers

`cros_typec_get_switch_handles` allocates four pointers when obtaining
type-c switch handles. These pointers are all freed if failing to obtain
any of them; therefore, pointers in `port` become stale. The stale
pointers eventually cause use-after-free or double free in later code
paths. Zeroing out all pointer fields after freeing to eliminate these
stale pointers.
References: https://git.kernel.org/stable/c/0ceadb5a3e45f1b81cf54bd496b40a5e50b6bd40; https://git.kernel.org/stable/c/6613f36a2fa5c69e528bccba8b3d831f759dad2f; https://git.kernel.org/stable/c/9a8aadcf0b459c1257b9477fd6402e1d5952ae07
CVE: CVE-2022-50643
Published: 2025-12-09
Description: In the Linux kernel, the following vulnerability has been resolved:

cifs: Fix xid leak in cifs_copy_file_range()

If the file is used by swap, before return -EOPNOTSUPP, should
free the xid, otherwise, the xid will be leaked.
References: https://git.kernel.org/stable/c/27cfd3afaab000a455194338db3b7f2031fde9d0; https://git.kernel.org/stable/c/9a97df404a402fe1174d2d1119f87ff2a0ca2fe9; https://git.kernel.org/stable/c/bf49d4fe4ab7b8d812927a2c7b514864d5fc1bb2
CVE: CVE-2022-50644
Published: 2025-12-09
Description: In the Linux kernel, the following vulnerability has been resolved:

clk: ti: dra7-atl: Fix reference leak in of_dra7_atl_clk_probe

pm_runtime_get_sync() will increment pm usage counter.
Forgetting to putting operation will result in reference leak.
Add missing pm_runtime_put_sync in some error paths.
References: https://git.kernel.org/stable/c/25fe7b0d596b343e7a5504ba11767115fff8494f; https://git.kernel.org/stable/c/27abe45df1dc394c184688d816cbbf2f194d4c6a; https://git.kernel.org/stable/c/3441076f83aace85f5d6ccd9ffb301ac6b874776
CVE: CVE-2022-50645
Published: 2025-12-09
Description: In the Linux kernel, the following vulnerability has been resolved:

EDAC/i10nm: fix refcount leak in pci_get_dev_wrapper()

As the comment of pci_get_domain_bus_and_slot() says, it returns
a PCI device with refcount incremented, so it doesn't need to
call an extra pci_dev_get() in pci_get_dev_wrapper(), and the PCI
device needs to be put in the error path.
References: https://git.kernel.org/stable/c/1adb2583cdbd75f379e3230a43a7412d373d499f; https://git.kernel.org/stable/c/2db53c7059167b63cc790366ef1a9e286e71980b; https://git.kernel.org/stable/c/3e255dc21031cc1f341584eb99a7f31598bf0be7
CVE: CVE-2022-50646
Published: 2025-12-09
Description: In the Linux kernel, the following vulnerability has been resolved:

scsi: hpsa: Fix possible memory leak in hpsa_init_one()

The hpda_alloc_ctlr_info() allocates h and its field reply_map. However, in
hpsa_init_one(), if alloc_percpu() failed, the hpsa_init_one() jumps to
clean1 directly, which frees h and leaks the h->reply_map.

Fix by calling hpda_free_ctlr_info() to release h->replay_map and h instead
free h directly.
References: https://git.kernel.org/stable/c/0aa7be66168b1e84b2581ffff3ccb54a6c804a1e; https://git.kernel.org/stable/c/9c9ff300e0de[PII_REDACTED]5d86f449340d454a0c; https://git.kernel.org/stable/c/bfe10a1d9fbccdf39f8449d62509f070d8aaaac1
CVE: CVE-2022-50647
Published: 2025-12-09
Description: In the Linux kernel, the following vulnerability has been resolved:

RISC-V: Make port I/O string accessors actually work

Fix port I/O string accessors such as `insb', `outsb', etc. which use
the physical PCI port I/O address rather than the corresponding memory
mapping to get at the requested location, which in turn breaks at least
accesses made by our parport driver to a PCIe parallel port such as:

PCI parallel port detected: 1415:c118, I/O at 0x1000(0x1008), IRQ 20
parport0: PC-style at 0x1000 (0x1008), irq 20, using FIFO [PCSPP,TRISTATE,COMPAT,EPP,ECP]

causing a memory access fault:

Unable to handle kernel access to user memory without uaccess routines at virtual address [PII_REDACTED]
Oops [#1]
Modules linked in:
CPU: 1 PID: 350 Comm: cat Not tainted 6.0.0-rc2-00283-g10d4879f9ef0-dirty #23
Hardware name: SiFive HiFive Unmatched A00 (DT)
epc : parport_pc_fifo_write_block_pio+0x266/0x416
 ra : parport_pc_fifo_write_block_pio+0xb4/0x416
epc : ffffffff80542c3e ra : ffffffff80542a8c sp : ffffffd88899fc60
 gp : ffffffff80fa2700 tp : ffffffd882b1e900 t0 : ffffffd883d0b000
 t1 : ffffffffff000002 t2 :[PII_REDACTED]330a38 s0 : ffffffd88899fcf0
 s1 : [PII_REDACTED] a0 : [PII_REDACTED] a1 : [PII_REDACTED]
 a2 : ffffffd883d0a010 a3 : [PII_REDACTED] a4 : 00000000ffff8fbb
 a5 : ffffffd883d0a001 a6 : [PII_REDACTED] a7 : ffffffc800000000
 s2 : ffffffffff000002 s3 : ffffffff80d28880 s4 : ffffffff80fa1f50
 s5 : [PII_REDACTED] s6 : [PII_REDACTED] s7 : ffffffd883d0a000
 s8 : [PII_REDACTED] s9 : ffffffff80dc1d80 s10: ffffffd8807e4000
 s11: [PII_REDACTED] t3 :[PII_REDACTED]0000ff t4 : 393044410a303930
 t5 : [PII_REDACTED] t6 : [PII_REDACTED]
status: [PII_REDACTED] badaddr: [PII_REDACTED] cause:[PII_REDACTED]00000f
[<ffffffff80543212>] parport_pc_compat_write_block_pio+0xfe/0x200
[<ffffffff8053bbc0>] parport_write+0x46/0xf8
[<ffffffff8050530e>] lp_write+0x158/0x2d2
[<ffffffff80185716>] vfs_write+0x8e/0x2c2
[<ffffffff80185a74>] ksys_write+0x52/0xc2
[<ffffffff80185af2>] sys_write+0xe/0x16
[<ffffffff80003770>] ret_from_syscall+0x0/0x2
---[ end trace [PII_REDACTED] ]---

For simplicity address the problem by adding PCI_IOBASE to the physical
address requested in the respective wrapper macros only, observing that
the raw accessors such as `__insb', `__outsb', etc. are not supposed to
be used other than by said macros.  Remove the cast to `long' that is no
longer needed on `addr' now that it is used as an offset from PCI_IOBASE
and add parentheses around `addr' needed for predictable evaluation in
macro expansion.  No need to make said adjustments in separate changes
given that current code is gravely broken and does not ever work.
References: https://git.kernel.org/stable/c/140b2b92dbefffa7f4f7211a1fd399a6e79e71c4; https://git.kernel.org/stable/c/1acee4616930fc07265cb8e539753a8062daa8e0; https://git.kernel.org/stable/c/2c60db6869fe5213471fcf4fe5704dc29da8b5ee
CVE: CVE-2022-50649
Published: 2025-12-09
Description: In the Linux kernel, the following vulnerability has been resolved:

power: supply: adp5061: fix out-of-bounds read in adp5061_get_chg_type()

ADP5061_CHG_STATUS_1_CHG_STATUS is masked with 0x07, which means a length
of 8, but adp5061_chg_type array size is 4, may end up reading 4 elements
beyond the end of the adp5061_chg_type[] array.
References: https://git.kernel.org/stable/c/038e4aa71281d0cbc8aeb56ba05ff7fc5653a106; https://git.kernel.org/stable/c/24a0be36e9a21f63de2e6088607e689e59ec15f4; https://git.kernel.org/stable/c/3376a0cf138dfc90b449fde541ca228a33e1c143
CVE: CVE-2022-50651
Published: 2025-12-09
Description: In the Linux kernel, the following vulnerability has been resolved:

ethtool: eeprom: fix null-deref on genl_info in dump

The similar fix as commit 46cdedf2a0fa ("ethtool: pse-pd: fix null-deref on
genl_info in dump") is also needed for ethtool eeprom.
References: https://git.kernel.org/stable/c/138a13d8f5c81266032af680f63069387f2748da; https://git.kernel.org/stable/c/1e3be98592a12511d4e78a9a67aaff3e6ca4980c; https://git.kernel.org/stable/c/9d9effca9d7d7cf6341182a7c5cabcbd6fa28063