Affected (full) in projects: openbmc - OpenGrok search results

Searched full:affected (Results 1 – 25 of 1027) sorted by relevance

/openbmc/openbmc/meta-openembedded/meta-oe/recipes-support/imagemagick/
H A D	imagemagick_7.1.1.bb	104 CVE_STATUS[CVE-2014-9804] = "cpe-incorrect: The current version (7.1.1) is not affected by the CVE … 105 CVE_STATUS[CVE-2014-9805] = "cpe-incorrect: The current version (7.1.1) is not affected by the CVE … 106 CVE_STATUS[CVE-2014-9806] = "cpe-incorrect: The current version (7.1.1) is not affected by the CVE … 107 CVE_STATUS[CVE-2014-9807] = "cpe-incorrect: The current version (7.1.1) is not affected by the CVE … 108 CVE_STATUS[CVE-2014-9808] = "cpe-incorrect: The current version (7.1.1) is not affected by the CVE … 109 CVE_STATUS[CVE-2014-9809] = "cpe-incorrect: The current version (7.1.1) is not affected by the CVE … 110 CVE_STATUS[CVE-2014-9810] = "cpe-incorrect: The current version (7.1.1) is not affected by the CVE … 111 CVE_STATUS[CVE-2014-9811] = "cpe-incorrect: The current version (7.1.1) is not affected by the CVE … 112 CVE_STATUS[CVE-2014-9812] = "cpe-incorrect: The current version (7.1.1) is not affected by the CVE … 113 CVE_STATUS[CVE-2014-9813] = "cpe-incorrect: The current version (7.1.1) is not affected by the CVE … [all …]
/openbmc/linux/Documentation/admin-guide/hw-vuln/
H A D	reg-file-data-sampling.rst	11 Affected Processors 13 Below is the list of affected Intel processors [#f1]_: 33 RAPTORLAKE(06_B7H) codenamed Catlow are not affected. They are reported as 34 vulnerable in Linux because they share the same family/model with an affected 35 part. Unlike their affected counterparts, they do not enumerate RFDS_CLEAR or 37 affected and unaffected parts, but it is deemed not worth adding complexity as 44 mitigation strategy to force the CPU to clear the affected buffers before an 47 The microcode clears the affected CPU buffers when the VERW instruction is 53 before VMentry. None of the affected cores support SMT, so VERW is not required 58 Newer processors and microcode update on existing affected processors added new [all …]
H A D	processor_mmio_stale_data.rst	9 are not affected. System environments using virtualization where MMIO access is 61 processors affected by FBSDP, this may expose stale data from the fill buffers 67 into client core fill buffers, processors affected by MFBDS can leak data from 77 Affected Processors 79 Not all the CPUs are affected by all the variants. For instance, most 83 Below is the list of affected Intel processors [#f1]_: 108 If a CPU is in the affected processor list, but not affected by a variant, it 115 Newer processors and microcode update on existing affected processors added new 122 Bit 13 - SBDR_SSDP_NO - When set, processor is not affected by either the 125 Bit 14 - FBSDP_NO - When set, processor is not affected by the Fill Buffer [all …]
H A D	mds.rst	8 Affected processors 23 Whether a processor is affected or not can be read out from the MDS 26 Not all processors are affected by all variants of MDS, but the mitigation 100 * - 'Not affected' 143 The kernel detects the affected CPUs and the presence of the microcode 146 If a CPU is affected and the microcode is available, then the kernel 156 The mitigation for MDS clears the affected CPU buffers on return to user 160 is only affected by MSBDS and not any other MDS variant, because the 163 For CPUs which are only affected by MSBDS the user space, guest and idle 164 transition mitigations are sufficient and SMT is not affected. [all …]
H A D	tsx_async_abort.rst	10 Affected processors 19 Whether a processor is affected or not can be read out from the TAA 99 …- The CPU is affected by this vulnerability and the microcode and kernel mitigation are not applie… 106 * - 'Not affected' 107 - The CPU is not affected by this issue. 131 The kernel detects the affected CPUs and the presence of the microcode which is 132 required. If a CPU is affected and the microcode is available, then the kernel 142 Affected systems where the host has TAA microcode and TAA is mitigated by 159 off This option disables the TAA mitigation on affected platforms. 161 is affected, the system is vulnerable. [all …]
H A D	special-register-buffer-data-sampling.rst	`17 Affected processors 20 be affected. 22 A processor is affected by SRBDS if its Family_Model and stepping is 25 latter class of processors are only affected when Intel TSX is enabled 26 by software using TSX_CTRL_MSR otherwise they are not affected. 118 affected platforms. 130 Not affected Processor not vulnerable 141 affected but with no way to know if host`
H A D	cross-thread-rsb.rst	`18 Affected processors 38 Affected SMT-capable processors support 1T and 2T modes of execution when SMT 46 In affected processors, the return address predictor (RAP) is partitioned 61 An attack can be mounted on affected processors by performing a series of CALL`
/openbmc/linux/Documentation/arch/x86/
H A D	mds.rst	74 thread case (SMT off): Force the CPU to clear the affected buffers. 78 the affected CPU buffers when the VERW instruction is executed. 83 VERW can be avoided. If the CPU is not affected by L1TF then VERW needs to 119 off Mitigation is disabled. Either the CPU is not affected or 122 full Mitigation is enabled. CPU is affected and MD_CLEAR is 125 vmwerv Mitigation is enabled. CPU is affected and MD_CLEAR is not 132 If the CPU is affected and mds=off is not supplied on the kernel command 143 on affected CPUs when the mitigation is not disabled on the kernel 174 cleared on affected CPUs when SMT is active. This addresses the 181 The idle clearing is enabled on CPUs which are only affected by MSBDS [all …]
/openbmc/linux/arch/x86/kernel/
H A D	smp.c	69 * 5AP. symmetric IO mode (normal Linux operation) not affected. 71 * 6AP. 'noapic' mode might be affected - fixed in later steppings 94 * 6AP. not affected - worked around in hardware 95 * 7AP. not affected - worked around in hardware 97 * 9AP. only 'noapic' mode affected. Might generate spurious 100 * 10AP. not affected - worked around in hardware 104 * 12AP. not affected - worked around in hardware 105 * 13AP. not affected - worked around in hardware 107 * 15AP. not affected - worked around in hardware 108 * 16AP. not affected - worked around in hardware [all …]
/openbmc/docs/security/
H A D	obmc-github-security-advisory-template.md	`12 ### Affected Product 14 Ecosystem: Other OpenBMC Package name: <TBD> Affected versions: 2.9 Patched 40 area or the function affected, and a description of the issue. There should be 52 ### Affected Release 58 Please include the commit-id in the affected repo, the commit id for the`
H A D	how-to-report-a-security-vulnerability.md	`18 - If you know which source code repository is affected, find the repository 28 separate owners. If you do not know which repository is affected, the owner or 60 - If the problem is not severe, please write an issue to the affected repository`
H A D	obmc-security-response-team-guidelines.md	`40 they are affected. Use Git tags and commit IDs if known. It also may be 41 helpful to say what OpenBMC version is affected. For example, if the 42 problem in the original code through OpenBMC release 2.9, the affected 72 - Publish a security advisory to the affected OpenBMC repository. 126 ...summary: include CVEs, releases affected, etc....`
/openbmc/linux/arch/arm64/
H A D	Kconfig	424 The affected design reports FEAT_HAFDBS as not implemented in 457 the kernel if an affected CPU is detected. 479 the kernel if an affected CPU is detected. 502 only patch the kernel if an affected CPU is detected. 524 the kernel if an affected CPU is detected. 535 Affected Cortex-A57 parts might deadlock when exclusive load/store 542 the kernel if an affected CPU is detected. 554 Affected Cortex-A57 parts might report a Stage 2 translation 563 the kernel if an affected CPU is detected. 575 Affected parts may corrupt the AES state if an interrupt is [all …]
/openbmc/linux/arch/alpha/kernel/
H A D	bugs.c	`25 return sprintf(buf, "Not affected\n"); in cpu_show_meltdown() 34 return sprintf(buf, "Not affected\n"); in cpu_show_spectre_v1() 43 return sprintf(buf, "Not affected\n"); in cpu_show_spectre_v2()`
/openbmc/linux/security/integrity/evm/
H A D	evm_main.c	424 * @dentry: pointer to the affected dentry 441 * @dentry: pointer to the affected dentry 558 * @dentry: pointer to the affected dentry 559 * @xattr_name: pointer to the affected extended attribute name 595 * @dentry: pointer to the affected dentry 596 * @xattr_name: pointer to the affected extended attribute name 645 * @dentry: pointer to the affected dentry 704 * @xattr_name: pointer to the affected extended attribute name 729 * @dentry: pointer to the affected dentry 730 * @xattr_name: pointer to the affected extended attribute name [all …]
/openbmc/linux/include/linux/
H A D	cpu_pm.h	`28 * CPU notifications apply to a single CPU and must be called on the affected 29 * CPU. They are used to save per-cpu context for affected blocks. 32 * are used to save any global context for affected blocks, and must be called`
/openbmc/openbmc/poky/scripts/contrib/
H A D	list-packageconfig-flags.py	`9 # - list available PACKAGECONFIG flags and all affected recipes 74 ''' Collect available PACKAGECONFIG flags and all affected pkgs ''' 102 ''' Display available PACKAGECONFIG flags and all affected pkgs ''' 140 help = "list available PACKAGECONFIG flags and affected recipes",`
/openbmc/openbmc/meta-openembedded/meta-oe/recipes-support/libraw/
H A D	libraw_0.21.2.bb	`13 CVE_STATUS[CVE-2020-22628] = "cpe-incorrect: The current version (0.21.2) is not affected by the CV… 14 CVE_STATUS[CVE-2023-1729] = "cpe-incorrect: The current version (0.21.2) is not affected by the CVE…`
/openbmc/openbmc/meta-openembedded/meta-gnome/recipes-gimp/gimp/
H A D	gimp_2.10.38.bb	`99 CVE_STATUS[CVE-2009-0581] = "cpe-incorrect: The current version (2.10.38) is not affected." 100 CVE_STATUS[CVE-2009-0723] = "cpe-incorrect: The current version (2.10.38) is not affected." 101 CVE_STATUS[CVE-2009-0733] = "cpe-incorrect: The current version (2.10.38) is not affected."`
/openbmc/u-boot/tools/binman/
H A D	state.py	`185 """Add a new property to affected device trees with an integer value of 0. 194 """Add a new subnode to a node in affected device trees 211 """Add a new string property to affected device trees 221 """Update an integer property in affected device trees with an integer value`
/openbmc/openbmc/poky/meta/files/common-licenses/
H A D	APSL-1.1	19 1.1 "Affected Original Code" means only those specific portions of 214 for Apple and You to continue using the Affected Original Code; (b) 215 modify the Affected Original Code so that it is no longer infringing; 217 distribute the Affected Original Code until a final determination of 225 modification, sublicensing and distribution of the Affected Original 226 Code, Apple will lift the suspension of rights to the Affected 229 Your rights to Affected Original Code, nothing in this License shall 231 law, from replacing the Affected Original Code with non-infringing
/openbmc/openbmc/meta-openembedded/meta-webserver/recipes-httpd/apache2/
H A D	apache2_2.4.62.bb	40 CVE_STATUS[CVE-1999-0289] = "not-applicable-platform: The current version (2.4.6) is not affected. … 41 CVE_STATUS[CVE-2007-0450] = "not-applicable-platform: The current version (2.4.6) is not affected. … 42 CVE_STATUS[CVE-2007-6421] = "cpe-incorrect: The current version (2.4.59) is not affected by the CVE… 43 CVE_STATUS[CVE-2007-6422] = "cpe-incorrect: The current version (2.4.59) is not affected by the CVE… 44 CVE_STATUS[CVE-2007-6423] = "cpe-incorrect: The current version (2.4.59) is not affected by the CVE… 45 CVE_STATUS[CVE-2008-2168] = "cpe-incorrect: The current version (2.4.59) is not affected by the CVE… 46 CVE_STATUS[CVE-2010-0425] = "not-applicable-platform: The current version (2.4.6) is not affected. …
/openbmc/u-boot/include/
H A D	reset.h	`26 * Reset consumers/clients are the HW modules affected by reset signals. This 159 * affected HW module(s). Depending on the reset controller hardware, the reset 173 * bulk struct, thus resetting the affected HW module(s). Depending on the 188 * affected HW modules() from reset, and allowing them to continue normal 202 * bulk struct, thus releasing the affected HW modules() from reset, and`
/openbmc/linux/Documentation/PCI/
H A D	pci-error-recovery.rst	18 pSeries boxes. A typical action taken is to disconnect the affected device, 22 offered, so that the affected PCI device(s) are reset and put back 24 between the affected device drivers and the PCI controller chip. 31 is reported as soon as possible to all affected device drivers, 129 every driver affected by the error. 174 thus, if one device sleeps/schedules, all devices are affected. 191 DMA), and then calls the mmio_enabled() callback on all affected 338 The platform will call the resume() callback on all affected device
/openbmc/linux/arch/x86/include/asm/
H A D	cpufeatures.h	458 #define X86_FEATURE_SRSO_NO (2032+29) / "" CPU is not affected by SRSO / 496 #define X86_BUG_AMD_E400 X86_BUG(13) / CPU is among the affected by Erratum 400 / 497 #define X86_BUG_CPU_MELTDOWN X86_BUG(14) / CPU is affected by meltdown attack and needs kernel pa… 498 #define X86_BUG_SPECTRE_V1 X86_BUG(15) /* CPU is affected by Spectre variant 1 attack with conditi… 499 #define X86_BUG_SPECTRE_V2 X86_BUG(16) /* CPU is affected by Spectre variant 2 attack with indirec… 500 #define X86_BUG_SPEC_STORE_BYPASS X86_BUG(17) /* CPU is affected by speculative store bypass attack… 501 #define X86_BUG_L1TF X86_BUG(18) /* CPU is affected by L1 Terminal Fault / 502 #define X86_BUG_MDS X86_BUG(19) / CPU is affected by Microarchitectural data sampling / 503 #define X86_BUG_MSBDS_ONLY X86_BUG(20) / CPU is only affected by the MSDBS variant of BUG_MDS / 504 #define X86_BUG_SWAPGS X86_BUG(21) / CPU is affected by speculation through SWAPGS */ [all …]

12 3 4 5 6 7 8 9 10 >>...42

Project(s)

Full Search
Definition
Symbol
File Path
History
Type