Vulnerabilities

With the aim of informing, warning and helping professionals with the latest security vulnerabilities in technology systems, we have made a database available for users interested in this information, which is in Spanish and includes all of the latest documented and recognised vulnerabilities.

This repository, with over 75,000 registers, is based on the information from the NVD (National Vulnerability Database) – by virtue of a partnership agreement – through which INCIBE translates the included information into Spanish.

On occasions this list will show vulnerabilities that have still not been translated, as they are added while the INCIBE team is still carrying out the translation process. The CVE  (Common Vulnerabilities and Exposures) Standard for Information Security Vulnerability Names is used with the aim to support the exchange of information between different tools and databases.

All vulnerabilities collected are linked to different information sources, as well as available patches or solutions provided by manufacturers and developers. It is possible to carry out advanced searches, as there is the option to select different criteria to narrow down the results, some examples being vulnerability types, manufacturers and impact levels, among others.

Through RSS feeds or Newsletters we can be informed daily about the latest vulnerabilities added to the repository. Below there is a list, updated daily, where you can discover the latest vulnerabilities.

CVE-2024-26742

Publication date:
03/04/2024
In the Linux kernel, the following vulnerability has been resolved:<br /> <br /> scsi: smartpqi: Fix disable_managed_interrupts<br /> <br /> Correct blk-mq registration issue with module parameter<br /> disable_managed_interrupts enabled.<br /> <br /> When we turn off the default PCI_IRQ_AFFINITY flag, the driver needs to<br /> register with blk-mq using blk_mq_map_queues(). The driver is currently<br /> calling blk_mq_pci_map_queues() which results in a stack trace and possibly<br /> undefined behavior.<br /> <br /> Stack Trace:<br /> [ 7.860089] scsi host2: smartpqi<br /> [ 7.871934] WARNING: CPU: 0 PID: 238 at block/blk-mq-pci.c:52 blk_mq_pci_map_queues+0xca/0xd0<br /> [ 7.889231] Modules linked in: sd_mod t10_pi sg uas smartpqi(+) crc32c_intel scsi_transport_sas usb_storage dm_mirror dm_region_hash dm_log dm_mod ipmi_devintf ipmi_msghandler fuse<br /> [ 7.924755] CPU: 0 PID: 238 Comm: kworker/0:3 Not tainted 4.18.0-372.88.1.el8_6_smartpqi_test.x86_64 #1<br /> [ 7.944336] Hardware name: HPE ProLiant DL380 Gen10/ProLiant DL380 Gen10, BIOS U30 03/08/2022<br /> [ 7.963026] Workqueue: events work_for_cpu_fn<br /> [ 7.978275] RIP: 0010:blk_mq_pci_map_queues+0xca/0xd0<br /> [ 7.978278] Code: 48 89 de 89 c7 e8 f6 0f 4f 00 3b 05 c4 b7 8e 01 72 e1 5b 31 c0 5d 41 5c 41 5d 41 5e 41 5f e9 7d df 73 00 31 c0 e9 76 df 73 00 0b eb bc 90 90 0f 1f 44 00 00 41 57 49 89 ff 41 56 41 55 41 54<br /> [ 7.978280] RSP: 0018:ffffa95fc3707d50 EFLAGS: 00010216<br /> [ 7.978283] RAX: 00000000ffffffff RBX: 0000000000000000 RCX: 0000000000000010<br /> [ 7.978284] RDX: 0000000000000004 RSI: 0000000000000000 RDI: ffff9190c32d4310<br /> [ 7.978286] RBP: 0000000000000000 R08: ffffa95fc3707d38 R09: ffff91929b81ac00<br /> [ 7.978287] R10: 0000000000000001 R11: ffffa95fc3707ac0 R12: 0000000000000000<br /> [ 7.978288] R13: ffff9190c32d4000 R14: 00000000ffffffff R15: ffff9190c4c950a8<br /> [ 7.978290] FS: 0000000000000000(0000) GS:ffff9193efc00000(0000) knlGS:0000000000000000<br /> [ 7.978292] CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033<br /> [ 8.172814] CR2: 000055d11166c000 CR3: 00000002dae10002 CR4: 00000000007706f0<br /> [ 8.172816] DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000<br /> [ 8.172817] DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400<br /> [ 8.172818] PKRU: 55555554<br /> [ 8.172819] Call Trace:<br /> [ 8.172823] blk_mq_alloc_tag_set+0x12e/0x310<br /> [ 8.264339] scsi_add_host_with_dma.cold.9+0x30/0x245<br /> [ 8.279302] pqi_ctrl_init+0xacf/0xc8e [smartpqi]<br /> [ 8.294085] ? pqi_pci_probe+0x480/0x4c8 [smartpqi]<br /> [ 8.309015] pqi_pci_probe+0x480/0x4c8 [smartpqi]<br /> [ 8.323286] local_pci_probe+0x42/0x80<br /> [ 8.337855] work_for_cpu_fn+0x16/0x20<br /> [ 8.351193] process_one_work+0x1a7/0x360<br /> [ 8.364462] ? create_worker+0x1a0/0x1a0<br /> [ 8.379252] worker_thread+0x1ce/0x390<br /> [ 8.392623] ? create_worker+0x1a0/0x1a0<br /> [ 8.406295] kthread+0x10a/0x120<br /> [ 8.418428] ? set_kthread_struct+0x50/0x50<br /> [ 8.431532] ret_from_fork+0x1f/0x40<br /> [ 8.444137] ---[ end trace 1bf0173d39354506 ]---
Severity CVSS v4.0: Pending analysis
Last modification:
17/03/2025

CVE-2024-26743

Publication date:
03/04/2024
In the Linux kernel, the following vulnerability has been resolved:<br /> <br /> RDMA/qedr: Fix qedr_create_user_qp error flow<br /> <br /> Avoid the following warning by making sure to free the allocated<br /> resources in case that qedr_init_user_queue() fail.<br /> <br /> -----------[ cut here ]-----------<br /> WARNING: CPU: 0 PID: 143192 at drivers/infiniband/core/rdma_core.c:874 uverbs_destroy_ufile_hw+0xcf/0xf0 [ib_uverbs]<br /> Modules linked in: tls target_core_user uio target_core_pscsi target_core_file target_core_iblock ib_srpt ib_srp scsi_transport_srp nfsd nfs_acl rpcsec_gss_krb5 auth_rpcgss nfsv4 dns_resolver nfs lockd grace fscache netfs 8021q garp mrp stp llc ext4 mbcache jbd2 opa_vnic ib_umad ib_ipoib sunrpc rdma_ucm ib_isert iscsi_target_mod target_core_mod ib_iser libiscsi scsi_transport_iscsi rdma_cm iw_cm ib_cm hfi1 intel_rapl_msr intel_rapl_common mgag200 qedr sb_edac drm_shmem_helper rdmavt x86_pkg_temp_thermal drm_kms_helper intel_powerclamp ib_uverbs coretemp i2c_algo_bit kvm_intel dell_wmi_descriptor ipmi_ssif sparse_keymap kvm ib_core rfkill syscopyarea sysfillrect video sysimgblt irqbypass ipmi_si ipmi_devintf fb_sys_fops rapl iTCO_wdt mxm_wmi iTCO_vendor_support intel_cstate pcspkr dcdbas intel_uncore ipmi_msghandler lpc_ich acpi_power_meter mei_me mei fuse drm xfs libcrc32c qede sd_mod ahci libahci t10_pi sg crct10dif_pclmul crc32_pclmul crc32c_intel qed libata tg3<br /> ghash_clmulni_intel megaraid_sas crc8 wmi [last unloaded: ib_srpt]<br /> CPU: 0 PID: 143192 Comm: fi_rdm_tagged_p Kdump: loaded Not tainted 5.14.0-408.el9.x86_64 #1<br /> Hardware name: Dell Inc. PowerEdge R430/03XKDV, BIOS 2.14.0 01/25/2022<br /> RIP: 0010:uverbs_destroy_ufile_hw+0xcf/0xf0 [ib_uverbs]<br /> Code: 5d 41 5c 41 5d 41 5e e9 0f 26 1b dd 48 89 df e8 67 6a ff ff 49 8b 86 10 01 00 00 48 85 c0 74 9c 4c 89 e7 e8 83 c0 cb dd eb 92 0b eb be 0f 0b be 04 00 00 00 48 89 df e8 8e f5 ff ff e9 6d ff<br /> RSP: 0018:ffffb7c6cadfbc60 EFLAGS: 00010286<br /> RAX: ffff8f0889ee3f60 RBX: ffff8f088c1a5200 RCX: 00000000802a0016<br /> RDX: 00000000802a0017 RSI: 0000000000000001 RDI: ffff8f0880042600<br /> RBP: 0000000000000001 R08: 0000000000000001 R09: 0000000000000000<br /> R10: ffff8f11fffd5000 R11: 0000000000039000 R12: ffff8f0d5b36cd80<br /> R13: ffff8f088c1a5250 R14: ffff8f1206d91000 R15: 0000000000000000<br /> FS: 0000000000000000(0000) GS:ffff8f11d7c00000(0000) knlGS:0000000000000000<br /> CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033<br /> CR2: 0000147069200e20 CR3: 00000001c7210002 CR4: 00000000001706f0<br /> Call Trace:<br /> <br /> ? show_trace_log_lvl+0x1c4/0x2df<br /> ? show_trace_log_lvl+0x1c4/0x2df<br /> ? ib_uverbs_close+0x1f/0xb0 [ib_uverbs]<br /> ? uverbs_destroy_ufile_hw+0xcf/0xf0 [ib_uverbs]<br /> ? __warn+0x81/0x110<br /> ? uverbs_destroy_ufile_hw+0xcf/0xf0 [ib_uverbs]<br /> ? report_bug+0x10a/0x140<br /> ? handle_bug+0x3c/0x70<br /> ? exc_invalid_op+0x14/0x70<br /> ? asm_exc_invalid_op+0x16/0x20<br /> ? uverbs_destroy_ufile_hw+0xcf/0xf0 [ib_uverbs]<br /> ib_uverbs_close+0x1f/0xb0 [ib_uverbs]<br /> __fput+0x94/0x250<br /> task_work_run+0x5c/0x90<br /> do_exit+0x270/0x4a0<br /> do_group_exit+0x2d/0x90<br /> get_signal+0x87c/0x8c0<br /> arch_do_signal_or_restart+0x25/0x100<br /> ? ib_uverbs_ioctl+0xc2/0x110 [ib_uverbs]<br /> exit_to_user_mode_loop+0x9c/0x130<br /> exit_to_user_mode_prepare+0xb6/0x100<br /> syscall_exit_to_user_mode+0x12/0x40<br /> do_syscall_64+0x69/0x90<br /> ? syscall_exit_work+0x103/0x130<br /> ? syscall_exit_to_user_mode+0x22/0x40<br /> ? do_syscall_64+0x69/0x90<br /> ? syscall_exit_work+0x103/0x130<br /> ? syscall_exit_to_user_mode+0x22/0x40<br /> ? do_syscall_64+0x69/0x90<br /> ? do_syscall_64+0x69/0x90<br /> ? common_interrupt+0x43/0xa0<br /> entry_SYSCALL_64_after_hwframe+0x72/0xdc<br /> RIP: 0033:0x1470abe3ec6b<br /> Code: Unable to access opcode bytes at RIP 0x1470abe3ec41.<br /> RSP: 002b:00007fff13ce9108 EFLAGS: 00000246 ORIG_RAX: 0000000000000010<br /> RAX: fffffffffffffffc RBX: 00007fff13ce9218 RCX: 00001470abe3ec6b<br /> RDX: 00007fff13ce9200 RSI: 00000000c0181b01 RDI: 0000000000000004<br /> RBP: 00007fff13ce91e0 R08: 0000558d9655da10 R09: 0000558d9655dd00<br /> R10: 00007fff13ce95c0 R11: 0000000000000246 R12: 00007fff13ce9358<br /> R13: 0000000000000013 R14: 0000558d9655db50 R15: 00007fff13ce9470<br /> <br /> --[ end trace 888a9b92e04c5c97 ]--
Severity CVSS v4.0: Pending analysis
Last modification:
17/03/2025

CVE-2024-26744

Publication date:
03/04/2024
In the Linux kernel, the following vulnerability has been resolved:<br /> <br /> RDMA/srpt: Support specifying the srpt_service_guid parameter<br /> <br /> Make loading ib_srpt with this parameter set work. The current behavior is<br /> that setting that parameter while loading the ib_srpt kernel module<br /> triggers the following kernel crash:<br /> <br /> BUG: kernel NULL pointer dereference, address: 0000000000000000<br /> Call Trace:<br /> <br /> parse_one+0x18c/0x1d0<br /> parse_args+0xe1/0x230<br /> load_module+0x8de/0xa60<br /> init_module_from_file+0x8b/0xd0<br /> idempotent_init_module+0x181/0x240<br /> __x64_sys_finit_module+0x5a/0xb0<br /> do_syscall_64+0x5f/0xe0<br /> entry_SYSCALL_64_after_hwframe+0x6e/0x76
Severity CVSS v4.0: Pending analysis
Last modification:
02/05/2025

CVE-2024-26747

Publication date:
03/04/2024
In the Linux kernel, the following vulnerability has been resolved:<br /> <br /> usb: roles: fix NULL pointer issue when put module&amp;#39;s reference<br /> <br /> In current design, usb role class driver will get usb_role_switch parent&amp;#39;s<br /> module reference after the user get usb_role_switch device and put the<br /> reference after the user put the usb_role_switch device. However, the<br /> parent device of usb_role_switch may be removed before the user put the<br /> usb_role_switch. If so, then, NULL pointer issue will be met when the user<br /> put the parent module&amp;#39;s reference.<br /> <br /> This will save the module pointer in structure of usb_role_switch. Then,<br /> we don&amp;#39;t need to find module by iterating long relations.
Severity CVSS v4.0: Pending analysis
Last modification:
04/04/2025

CVE-2024-26748

Publication date:
03/04/2024
In the Linux kernel, the following vulnerability has been resolved:<br /> <br /> usb: cdns3: fix memory double free when handle zero packet<br /> <br /> 829 if (request-&gt;complete) {<br /> 830 spin_unlock(&amp;priv_dev-&gt;lock);<br /> 831 usb_gadget_giveback_request(&amp;priv_ep-&gt;endpoint,<br /> 832 request);<br /> 833 spin_lock(&amp;priv_dev-&gt;lock);<br /> 834 }<br /> 835<br /> 836 if (request-&gt;buf == priv_dev-&gt;zlp_buf)<br /> 837 cdns3_gadget_ep_free_request(&amp;priv_ep-&gt;endpoint, request);<br /> <br /> Driver append an additional zero packet request when queue a packet, which<br /> length mod max packet size is 0. When transfer complete, run to line 831,<br /> usb_gadget_giveback_request() will free this requestion. 836 condition is<br /> true, so cdns3_gadget_ep_free_request() free this request again.<br /> <br /> Log:<br /> <br /> [ 1920.140696][ T150] BUG: KFENCE: use-after-free read in cdns3_gadget_giveback+0x134/0x2c0 [cdns3]<br /> [ 1920.140696][ T150]<br /> [ 1920.151837][ T150] Use-after-free read at 0x000000003d1cd10b (in kfence-#36):<br /> [ 1920.159082][ T150] cdns3_gadget_giveback+0x134/0x2c0 [cdns3]<br /> [ 1920.164988][ T150] cdns3_transfer_completed+0x438/0x5f8 [cdns3]<br /> <br /> Add check at line 829, skip call usb_gadget_giveback_request() if it is<br /> additional zero length packet request. Needn&amp;#39;t call<br /> usb_gadget_giveback_request() because it is allocated in this driver.
Severity CVSS v4.0: Pending analysis
Last modification:
14/01/2025

CVE-2024-26749

Publication date:
03/04/2024
In the Linux kernel, the following vulnerability has been resolved:<br /> <br /> usb: cdns3: fixed memory use after free at cdns3_gadget_ep_disable()<br /> <br /> ...<br /> cdns3_gadget_ep_free_request(&amp;priv_ep-&gt;endpoint, &amp;priv_req-&gt;request);<br /> list_del_init(&amp;priv_req-&gt;list);<br /> ...<br /> <br /> &amp;#39;priv_req&amp;#39; actually free at cdns3_gadget_ep_free_request(). But<br /> list_del_init() use priv_req-&gt;list after it.<br /> <br /> [ 1542.642868][ T534] BUG: KFENCE: use-after-free read in __list_del_entry_valid+0x10/0xd4<br /> [ 1542.642868][ T534]<br /> [ 1542.653162][ T534] Use-after-free read at 0x000000009ed0ba99 (in kfence-#3):<br /> [ 1542.660311][ T534] __list_del_entry_valid+0x10/0xd4<br /> [ 1542.665375][ T534] cdns3_gadget_ep_disable+0x1f8/0x388 [cdns3]<br /> [ 1542.671571][ T534] usb_ep_disable+0x44/0xe4<br /> [ 1542.675948][ T534] ffs_func_eps_disable+0x64/0xc8<br /> [ 1542.680839][ T534] ffs_func_set_alt+0x74/0x368<br /> [ 1542.685478][ T534] ffs_func_disable+0x18/0x28<br /> <br /> Move list_del_init() before cdns3_gadget_ep_free_request() to resolve this<br /> problem.
Severity CVSS v4.0: Pending analysis
Last modification:
14/01/2025

CVE-2024-26751

Publication date:
03/04/2024
In the Linux kernel, the following vulnerability has been resolved:<br /> <br /> ARM: ep93xx: Add terminator to gpiod_lookup_table<br /> <br /> Without the terminator, if a con_id is passed to gpio_find() that<br /> does not exist in the lookup table the function will not stop looping<br /> correctly, and eventually cause an oops.
Severity CVSS v4.0: Pending analysis
Last modification:
17/03/2025

CVE-2024-26752

Publication date:
03/04/2024
In the Linux kernel, the following vulnerability has been resolved:<br /> <br /> l2tp: pass correct message length to ip6_append_data<br /> <br /> l2tp_ip6_sendmsg needs to avoid accounting for the transport header<br /> twice when splicing more data into an already partially-occupied skbuff.<br /> <br /> To manage this, we check whether the skbuff contains data using<br /> skb_queue_empty when deciding how much data to append using<br /> ip6_append_data.<br /> <br /> However, the code which performed the calculation was incorrect:<br /> <br /> ulen = len + skb_queue_empty(&amp;sk-&gt;sk_write_queue) ? transhdrlen : 0;<br /> <br /> ...due to C operator precedence, this ends up setting ulen to<br /> transhdrlen for messages with a non-zero length, which results in<br /> corrupted packets on the wire.<br /> <br /> Add parentheses to correct the calculation in line with the original<br /> intent.
Severity CVSS v4.0: Pending analysis
Last modification:
17/03/2025

CVE-2024-26753

Publication date:
03/04/2024
In the Linux kernel, the following vulnerability has been resolved:<br /> <br /> crypto: virtio/akcipher - Fix stack overflow on memcpy<br /> <br /> sizeof(struct virtio_crypto_akcipher_session_para) is less than<br /> sizeof(struct virtio_crypto_op_ctrl_req::u), copying more bytes from<br /> stack variable leads stack overflow. Clang reports this issue by<br /> commands:<br /> make -j CC=clang-14 mrproper &gt;/dev/null 2&gt;&amp;1<br /> make -j O=/tmp/crypto-build CC=clang-14 allmodconfig &gt;/dev/null 2&gt;&amp;1<br /> make -j O=/tmp/crypto-build W=1 CC=clang-14 drivers/crypto/virtio/<br /> virtio_crypto_akcipher_algs.o
Severity CVSS v4.0: Pending analysis
Last modification:
27/02/2025

CVE-2024-26739

Publication date:
03/04/2024
In the Linux kernel, the following vulnerability has been resolved:<br /> <br /> net/sched: act_mirred: don&amp;#39;t override retval if we already lost the skb<br /> <br /> If we&amp;#39;re redirecting the skb, and haven&amp;#39;t called tcf_mirred_forward(),<br /> yet, we need to tell the core to drop the skb by setting the retcode<br /> to SHOT. If we have called tcf_mirred_forward(), however, the skb<br /> is out of our hands and returning SHOT will lead to UaF.<br /> <br /> Move the retval override to the error path which actually need it.
Severity CVSS v4.0: Pending analysis
Last modification:
25/11/2025

CVE-2024-20368

Publication date:
03/04/2024
A vulnerability in the web-based management interface of Cisco Identity Services Engine (ISE) could allow an unauthenticated, remote attacker to conduct a cross-site request forgery (CSRF) attack and perform arbitrary actions on an affected device.<br /> <br /> This vulnerability is due to insufficient CSRF protections for the web-based management interface of an affected device. An attacker could exploit this vulnerability by persuading a user of the interface to follow a crafted link. A successful exploit could allow the attacker to perform arbitrary actions on the affected device with the privileges of the targeted user.
Severity CVSS v4.0: Pending analysis
Last modification:
28/04/2025

CVE-2024-26728

Publication date:
03/04/2024
In the Linux kernel, the following vulnerability has been resolved:<br /> <br /> drm/amd/display: fix null-pointer dereference on edid reading<br /> <br /> Use i2c adapter when there isn&amp;#39;t aux_mode in dc_link to fix a<br /> null-pointer derefence that happens when running<br /> igt@kms_force_connector_basic in a system with DCN2.1 and HDMI connector<br /> detected as below:<br /> <br /> [ +0.178146] BUG: kernel NULL pointer dereference, address: 00000000000004c0<br /> [ +0.000010] #PF: supervisor read access in kernel mode<br /> [ +0.000005] #PF: error_code(0x0000) - not-present page<br /> [ +0.000004] PGD 0 P4D 0<br /> [ +0.000006] Oops: 0000 [#1] PREEMPT SMP NOPTI<br /> [ +0.000006] CPU: 15 PID: 2368 Comm: kms_force_conne Not tainted 6.5.0-asdn+ #152<br /> [ +0.000005] Hardware name: HP HP ENVY x360 Convertible 13-ay1xxx/8929, BIOS F.01 07/14/2021<br /> [ +0.000004] RIP: 0010:i2c_transfer+0xd/0x100<br /> [ +0.000011] Code: ea fc ff ff 66 0f 1f 84 00 00 00 00 00 90 90 90 90 90 90 90 90 90 90 90 90 90 90 90 90 f3 0f 1e fa 0f 1f 44 00 00 41 54 55 53 8b 47 10 48 89 fb 48 83 38 00 0f 84 b3 00 00 00 83 3d 2f 80 16<br /> [ +0.000004] RSP: 0018:ffff9c4f89c0fad0 EFLAGS: 00010246<br /> [ +0.000005] RAX: 0000000000000000 RBX: 0000000000000005 RCX: 0000000000000080<br /> [ +0.000003] RDX: 0000000000000002 RSI: ffff9c4f89c0fb20 RDI: 00000000000004b0<br /> [ +0.000003] RBP: ffff9c4f89c0fb80 R08: 0000000000000080 R09: ffff8d8e0b15b980<br /> [ +0.000003] R10: 00000000000380e0 R11: 0000000000000000 R12: 0000000000000080<br /> [ +0.000002] R13: 0000000000000002 R14: ffff9c4f89c0fb0e R15: ffff9c4f89c0fb0f<br /> [ +0.000004] FS: 00007f9ad2176c40(0000) GS:ffff8d90fe9c0000(0000) knlGS:0000000000000000<br /> [ +0.000003] CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033<br /> [ +0.000004] CR2: 00000000000004c0 CR3: 0000000121bc4000 CR4: 0000000000750ee0<br /> [ +0.000003] PKRU: 55555554<br /> [ +0.000003] Call Trace:<br /> [ +0.000006] <br /> [ +0.000006] ? __die+0x23/0x70<br /> [ +0.000011] ? page_fault_oops+0x17d/0x4c0<br /> [ +0.000008] ? preempt_count_add+0x6e/0xa0<br /> [ +0.000008] ? srso_alias_return_thunk+0x5/0x7f<br /> [ +0.000011] ? exc_page_fault+0x7f/0x180<br /> [ +0.000009] ? asm_exc_page_fault+0x26/0x30<br /> [ +0.000013] ? i2c_transfer+0xd/0x100<br /> [ +0.000010] drm_do_probe_ddc_edid+0xc2/0x140 [drm]<br /> [ +0.000067] ? srso_alias_return_thunk+0x5/0x7f<br /> [ +0.000006] ? _drm_do_get_edid+0x97/0x3c0 [drm]<br /> [ +0.000043] ? __pfx_drm_do_probe_ddc_edid+0x10/0x10 [drm]<br /> [ +0.000042] edid_block_read+0x3b/0xd0 [drm]<br /> [ +0.000043] _drm_do_get_edid+0xb6/0x3c0 [drm]<br /> [ +0.000041] ? __pfx_drm_do_probe_ddc_edid+0x10/0x10 [drm]<br /> [ +0.000043] drm_edid_read_custom+0x37/0xd0 [drm]<br /> [ +0.000044] amdgpu_dm_connector_mode_valid+0x129/0x1d0 [amdgpu]<br /> [ +0.000153] drm_connector_mode_valid+0x3b/0x60 [drm_kms_helper]<br /> [ +0.000000] __drm_helper_update_and_validate+0xfe/0x3c0 [drm_kms_helper]<br /> [ +0.000000] ? amdgpu_dm_connector_get_modes+0xb6/0x520 [amdgpu]<br /> [ +0.000000] ? srso_alias_return_thunk+0x5/0x7f<br /> [ +0.000000] drm_helper_probe_single_connector_modes+0x2ab/0x540 [drm_kms_helper]<br /> [ +0.000000] status_store+0xb2/0x1f0 [drm]<br /> [ +0.000000] kernfs_fop_write_iter+0x136/0x1d0<br /> [ +0.000000] vfs_write+0x24d/0x440<br /> [ +0.000000] ksys_write+0x6f/0xf0<br /> [ +0.000000] do_syscall_64+0x60/0xc0<br /> [ +0.000000] ? srso_alias_return_thunk+0x5/0x7f<br /> [ +0.000000] ? syscall_exit_to_user_mode+0x2b/0x40<br /> [ +0.000000] ? srso_alias_return_thunk+0x5/0x7f<br /> [ +0.000000] ? do_syscall_64+0x6c/0xc0<br /> [ +0.000000] ? do_syscall_64+0x6c/0xc0<br /> [ +0.000000] entry_SYSCALL_64_after_hwframe+0x6e/0xd8<br /> [ +0.000000] RIP: 0033:0x7f9ad46b4b00<br /> [ +0.000000] Code: 40 00 48 8b 15 19 b3 0d 00 f7 d8 64 89 02 48 c7 c0 ff ff ff ff eb b7 0f 1f 00 80 3d e1 3a 0e 00 00 74 17 b8 01 00 00 00 0f 05 3d 00 f0 ff ff 77 58 c3 0f 1f 80 00 00 00 00 48 83 ec 28 48 89<br /> [ +0.000000] RSP: 002b:00007ffcbd3bd6d8 EFLAGS: 00000202 ORIG_RAX: 0000000000000001<br /> [ +0.000000] RAX: ffffffffffffffda RBX: 0000000000000000 RCX: 00007f9ad46b4b00<br /> [ +0.000000] RDX: 0000000000000002 RSI: 00007f9ad48a7417 RDI: 0000000000000009<br /> [ +0.000000] RBP: 0000000000000002 R08<br /> ---truncated---
Severity CVSS v4.0: Pending analysis
Last modification:
07/01/2025