| /linux-6.15/drivers/gpu/drm/vc4/ |
| H A D | vc4_validate.c | 53 void *untrusted 144 return (untrusted - 1 == exec->bin_u + pos); in validate_bin_pos() 267 uint32_t length = *(uint32_t *)(untrusted + 1); in validate_indexed_prim_list() 268 uint32_t offset = *(uint32_t *)(untrusted + 5); in validate_indexed_prim_list() 269 uint32_t max_index = *(uint32_t *)(untrusted + 9); in validate_indexed_prim_list() 302 uint32_t length = *(uint32_t *)(untrusted + 1); in validate_gl_array_primitive() 303 uint32_t base_index = *(uint32_t *)(untrusted + 5); in validate_gl_array_primitive() 369 exec->bin_tiles_x = *(uint8_t *)(untrusted + 12); in validate_tile_binning_config() 370 exec->bin_tiles_y = *(uint8_t *)(untrusted + 13); in validate_tile_binning_config() 372 flags = *(uint8_t *)(untrusted + 14); in validate_tile_binning_config() [all …]
|
| /linux-6.15/Documentation/arch/x86/ |
| H A D | buslock.rst | 86 "untrusted" user processes on other cores. The hard real time cannot afford 87 to have any bus lock from the untrusted processes to hurt real time 89 solutions as they have no way to prevent the "untrusted" user code from
|
| H A D | mds.rst | 65 There is one exception, which is untrusted BPF. The functionality of 66 untrusted BPF is limited, but it needs to be thoroughly investigated
|
| H A D | tdx.rst | 292 information in shared memory, exposing it to the untrusted hypervisor. 308 userspace are completely untrusted.
|
| /linux-6.15/Documentation/admin-guide/hw-vuln/ |
| H A D | l1tf.rst | 258 which run untrusted guests, reduces the attack vector space. 260 Whether the interrupts with are affine to CPUs, which run untrusted 472 3. Virtualization with untrusted guests 521 affinity to the CPUs which run the untrusted guests can depending on 590 SMT systems vulnerable when running untrusted guests with EPT enabled. 597 - If regular users run untrusted guests on their machine, then L1TF is 598 just an add on to other malware which might be embedded in an untrusted 601 There is no technical way to prevent a user from running untrusted code
|
| H A D | core-scheduling.rst | 167 core. But there could be small window of time during which untrusted tasks run 204 Another approach to resolve these would be to make every untrusted task on the 205 system to not trust every other untrusted task. While this could reduce 206 parallelism of the untrusted tasks, it would still solve the above issues while
|
| H A D | multihit.rst | 163 3. Virtualization with untrusted guests 165 If the guest comes from an untrusted source, the guest host kernel will need
|
| H A D | mds.rst | 273 execute untrusted code which is supplied externally, then the mitigation 282 3. Virtualization with untrusted guests 301 SMT systems vulnerable when running untrusted code. The same rationale as
|
| H A D | tsx_async_abort.rst | 247 untrusted code which is supplied externally, then the mitigation can be 254 If there are untrusted applications or guests on the system, enabling TSX
|
| H A D | spectre.rst | 318 If SMT is used, Spectre variant 2 attacks from an untrusted guest 584 in use, an untrusted guest running in the sibling thread can have 616 execute externally supplied untrusted code, then the mitigations can 627 3. Sandbox untrusted programs 633 This prevents untrusted programs from polluting the branch target
|
| H A D | processor_mmio_stale_data.rst | 10 provided to untrusted guests may need mitigation. These vulnerabilities are 145 is more critical, or the untrusted software has no MMIO access). Note that
|
| /linux-6.15/Documentation/ABI/testing/ |
| H A D | securityfs-secrets-coco | 12 and therefore are not readable by the untrusted host.
|
| H A D | sysfs-class-bdi | 123 affordable for given relatively slow (or untrusted) device. Turning
|
| /linux-6.15/Documentation/security/ |
| H A D | snp-tdx-threat-model.rst | 111 coming from there is generally considered untrusted, unless userspace is 190 guest Linux kernel towards an untrusted host that is not covered by the 201 data should also be considered untrusted until its integrity and
|
| H A D | landlock.rst | 15 backdoored (i.e. untrusted), Landlock's features must be safe to use from the
|
| /linux-6.15/Documentation/userspace-api/ |
| H A D | check_exec.rst | 79 careful to not let untrusted users control this configuration. 139 The threat is malicious scripts run by untrusted users (but trusted code).
|
| /linux-6.15/drivers/pci/ |
| H A D | ats.c | 46 return (dev->untrusted == 0); in pci_ats_supported()
|
| H A D | probe.c | 1704 if (parent->untrusted) { in set_pcie_untrusted() 1705 dev->untrusted = true; in set_pcie_untrusted() 1711 dev->untrusted = true; in set_pcie_untrusted()
|
| /linux-6.15/drivers/iommu/ |
| H A D | iommu.c | 1808 struct device *untrusted = NULL; in iommu_get_default_domain_type() local 1830 if (dev_is_pci(gdev->dev) && to_pci_dev(gdev->dev)->untrusted) { in iommu_get_default_domain_type() 1837 untrusted = gdev->dev; in iommu_get_default_domain_type() 1853 if (untrusted) { in iommu_get_default_domain_type() 1856 untrusted, in iommu_get_default_domain_type()
|
| /linux-6.15/Documentation/admin-guide/aoe/ |
| H A D | aoe.rst | 53 untrusted networks should be ignored as a matter of security. See
|
| /linux-6.15/certs/ |
| H A D | Kconfig | 114 Keys in the keyring are considered entirely untrusted. Keys in this
|
| /linux-6.15/Documentation/core-api/ |
| H A D | swiotlb.rst | 51 "untrusted", the device should be given access only to the memory containing 54 IOMMU access control is per-granule, the untrusted device can gain access to 135 "alloc_align_mask" parameter is used by IOMMU code when mapping for untrusted
|
| /linux-6.15/Documentation/networking/ |
| H A D | ipvlan.rst | 132 (c) If the slave device is to be put into the hostile / untrusted network
|
| /linux-6.15/Documentation/admin-guide/LSM/ |
| H A D | SafeSetID.rst | 35 other untrusted uids without full blown CAP_SETUID capabilities. The non-root
|
| /linux-6.15/Documentation/filesystems/ |
| H A D | overlayfs.rst | 399 Do not use metacopy=on with untrusted upper/lower directories. Otherwise 404 for untrusted layers like from a pen drive. 498 an untrusted lower layer can be used to supply validated file content 499 for all metacopy files. If additionally the untrusted lower
|