Export limit exceeded: 425645 CVEs match your query. Please refine your search to export 10,000 CVEs or fewer.
Search
Search Results (425645 CVEs found)
| CVE | Vendors | Products | Updated | CVSS v3.1 |
|---|---|---|---|---|
| CVE-2026-63811 | 1 Linux | 1 Linux Kernel | 2026-11-10 | 5.5 Medium |
| In the Linux kernel, the following vulnerability has been resolved: f2fs: read COW data with the original inode during atomic write When updating an atomic-write file, f2fs_write_begin() may read the previously written data back from the COW inode: prepare_atomic_write_begin() locates the block in the COW inode and sets use_cow, and the read bio is then built with the COW inode: f2fs_submit_page_read(use_cow ? F2FS_I(inode)->cow_inode : inode, ...); and f2fs_grab_read_bio() decides whether to schedule fs-layer decryption (STEP_DECRYPT) for the bio based on that inode via fscrypt_inode_uses_fs_layer_crypto(). However, the folio being filled belongs to the original inode (folio->mapping->host == inode), and the data stored in the COW block was encrypted (or left as plaintext) using the original inode's context, not the COW inode's -- see f2fs_encrypt_one_page(), which keys off fio->page->mapping->host. fscrypt_decrypt_pagecache_blocks() likewise operates on folio->mapping->host. The COW inode is created as a tmpfile in the parent directory and inherits its encryption policy from there. With test_dummy_encryption the newly created COW inode gets the dummy policy and becomes encrypted, while a pre-existing regular file -- created before the policy applied, e.g. already present in the on-disk image -- stays unencrypted. The read path then sets STEP_DECRYPT based on the encrypted COW inode and calls fscrypt_decrypt_pagecache_blocks() on a folio whose host (the unencrypted original inode) has a NULL ->i_crypt_info, dereferencing it: Oops: general protection fault, probably for non-canonical address ... KASAN: null-ptr-deref in range [0x0000000000000008-0x000000000000000f] RIP: 0010:fscrypt_decrypt_pagecache_blocks+0xa0/0x310 Workqueue: f2fs_post_read_wq f2fs_post_read_work Call Trace: fscrypt_decrypt_bio+0x1eb/0x340 f2fs_post_read_work+0xba/0x140 process_one_work+0x91c/0x1a40 worker_thread+0x677/0xe90 kthread+0x2bc/0x3a0 The COW inode is only needed to locate the on-disk block, and that block address is already resolved into @blkaddr by prepare_atomic_write_begin() via __find_data_block(cow_inode, ...); f2fs_submit_page_read() then reads from that physical @blkaddr directly, so the inode argument only selects the post-read crypto context, not which block is fetched. Reading with @inode therefore returns the same (latest, not-yet-committed) COW data, while making both the fs-layer decryption decision and the inline crypto path use the correct (original inode's) key. With the COW inode no longer used at the read site, the use_cow flag has no remaining consumer; drop it from f2fs_write_begin() and prepare_atomic_write_begin(). | ||||
| CVE-2026-58844 | 1 Google | 1 Android | 2026-11-10 | 8.4 High |
| In multiple locations, there is a possible out of bounds read/write due to an incorrect bounds check. This could lead to local escalation of privilege with no additional execution privileges needed. User interaction is not needed for exploitation. | ||||
| CVE-2026-123849 | 1 Jetbrains | 1 Intellij Idea | 2026-11-10 | 7 High |
| In JetBrains IntelliJ IDEA before 2026.3 code execution was possible in untrusted projects via the Terraform File Watchers | ||||
| CVE-2026-123848 | 1 Jetbrains | 1 Intellij Idea | 2026-11-10 | 7.4 High |
| In JetBrains IntelliJ IDEA before 2026.3 host name verification was missing for server TLS certificates | ||||
| CVE-2026-123847 | 1 Jetbrains | 1 Intellij Idea | 2026-11-10 | 5.3 Medium |
| In JetBrains IntelliJ IDEA before 2026.3 command execution was possible via control characters in terminal command completion | ||||
| CVE-2026-123846 | 1 Jetbrains | 1 Intellij Idea | 2026-11-10 | 4.3 Medium |
| In JetBrains IntelliJ IDEA before 2026.3 blind SSRF was possible via remote references in JSON Schema validation | ||||
| CVE-2026-123845 | 1 Jetbrains | 1 Intellij Idea | 2026-11-10 | 3.3 Low |
| In JetBrains IntelliJ IDEA before 2026.3 path traversal was possible via JSON Schema references in untrusted projects | ||||
| CVE-2026-123844 | 1 Jetbrains | 1 Intellij Idea | 2026-11-10 | 5.3 Medium |
| In JetBrains IntelliJ IDEA before 2026.3 sSRF was possible via custom plugin repositories | ||||
| CVE-2026-123843 | 1 Jetbrains | 1 Intellij Idea | 2026-11-10 | 3.3 Low |
| In JetBrains IntelliJ IDEA before 2026.3 untrusted projects could trigger changes to GPG agent configuration | ||||
| CVE-2026-123842 | 1 Jetbrains | 1 Intellij Idea | 2026-11-10 | 7.1 High |
| In JetBrains IntelliJ IDEA before 2026.3 arbitrary file write was possible via symlinks when extracting plugin archives | ||||
| CVE-2026-123841 | 1 Jetbrains | 1 Intellij Idea | 2026-11-10 | 7.8 High |
| In JetBrains IntelliJ IDEA before 2026.3 code execution was possible via symlinks in an imported settings archive | ||||
| CVE-2026-123840 | 1 Jetbrains | 1 Intellij Idea | 2026-11-10 | 4.7 Medium |
| In JetBrains IntelliJ IDEA before 2026.3 hTML injection was possible in Remote Development editor tabs | ||||
| CVE-2026-123308 | 1 Jetbrains | 1 Intellij Idea | 2026-11-10 | 6.3 Medium |
| In JetBrains IntelliJ IDEA before 2026.3 code execution via the document import was possible in untrusted projects | ||||
| CVE-2026-123309 | 1 Jetbrains | 1 Intellij Idea | 2026-11-10 | 6.1 Medium |
| In JetBrains IntelliJ IDEA before 2026.3, 2026.2.4 stored XSS was possible on the built-in web server via Markdown preview | ||||
| CVE-2026-123310 | 1 Jetbrains | 1 Intellij Idea | 2026-11-10 | 5.4 Medium |
| In JetBrains IntelliJ IDEA before 2026.3 kotlin scripts could trigger dependency downloads from arbitrary repositories in untrusted projects | ||||
| CVE-2026-123311 | 1 Jetbrains | 1 Intellij Idea | 2026-11-10 | 5.3 Medium |
| In JetBrains IntelliJ IDEA before 2026.3, 2026.2.4 command execution via a hidden run control in the Markdown preview was possible | ||||
| CVE-2026-123312 | 1 Jetbrains | 1 Intellij Idea | 2026-11-10 | 3.3 Low |
| In JetBrains IntelliJ IDEA before 2026.3, 2026.2.4 sSRF was possible via annotations.xml files during indexing | ||||
| CVE-2026-123313 | 1 Jetbrains | 1 Intellij Idea | 2026-11-10 | 3.3 Low |
| In JetBrains IntelliJ IDEA before 2026.3 improper checks could enable disabled plugins via external dependency settings | ||||
| CVE-2026-123314 | 1 Jetbrains | 1 Intellij Idea | 2026-11-10 | 3.1 Low |
| In JetBrains IntelliJ IDEA before 2026.3, 2026.2.4 xXE attack was possible via an XML response to an HTTP Client request | ||||
| CVE-2026-123833 | 1 Jetbrains | 1 Intellij Idea | 2026-11-10 | 3.6 Low |
| In JetBrains IntelliJ IDEA before 2026.3 database connections could be established in untrusted projects | ||||