Home
last modified time | relevance | path

Searched full:flaw (Results 1 – 25 of 35) sorted by relevance

12

/openbmc/openbmc/poky/meta/files/common-licenses/
H A DCAL-1.0-Combined-Work-Exception150 vulnerability or a security flaw in the Work,
152 + b) disclosure of the vulnerability or security flaw before the end
157 vulnerability or security flaw with one or more additional Licensees,
H A DCAL-1.0150 vulnerability or a security flaw in the Work,
152 + b) disclosure of the vulnerability or security flaw before the end
157 vulnerability or security flaw with one or more additional Licensees,
/openbmc/linux/Documentation/devicetree/bindings/input/
H A Dgoodix,gt7375p.yaml55 Due to potential touchscreen hardware flaw, back-powering could happen in
/openbmc/linux/Documentation/security/
H A Dself-protection.rst8 entire classes of bugs, blocking security flaw exploitation methods,
185 flaw. By trapping atomic wrapping, this class of bug vanishes.
210 flaw.
/openbmc/openbmc/poky/meta/recipes-graphics/xorg-xserver/
H A Dxserver-xorg.inc26 As per upstream, exploiting this flaw is non-trivial and it requires exact \
30 available for this flaw."
/openbmc/openbmc/poky/documentation/dev-manual/
H A Dsecurity-subjects.rst73 If you find a security flaw: a crash, an information leakage, or anything that
146 the flaw to the upstream project. Normally the upstream project analyzes the
/openbmc/u-boot/doc/
H A DREADME.memory-test70 fundamental, unfixable design flaw: they are based on the assumption
/openbmc/linux/Documentation/admin-guide/sysctl/
H A Dfs.rst193 directories like ``/tmp``. The common method of exploitation of this flaw
229 directories like ``/tmp``. The common method of exploitation of this flaw
/openbmc/linux/Documentation/translations/sp_SP/process/
H A Dresearcher-guidelines.rst114 This flaw was found using an experimental static analysis tool we are
/openbmc/linux/Documentation/process/
H A Dresearcher-guidelines.rst134 This flaw was found using an experimental static analysis tool we are
H A Dembargoed-hardware-issues.rst48 identified a potential hardware flaw.
/openbmc/linux/tools/testing/selftests/x86/
H A Dsingle_step_syscall.c179 * SYSENTER: it triggers a nasty design flaw in SYSENTER. in main()
/openbmc/qemu/util/
H A Dkeyval.c63 * Design flaw: there is no way to denote an empty array or non-root
70 * Design flaw: scalar values can only be strings; there is no way to
/openbmc/linux/Documentation/admin-guide/hw-vuln/
H A Dl1tf.rst97 share the L1 Data Cache (L1D) is important for this. As the flaw allows
295 activated. Due to a design flaw of Intel processors related
/openbmc/linux/drivers/scsi/isci/
H A Disci.h172 * an operation due to a critical flaw the prevents any further operation
/openbmc/linux/drivers/scsi/
H A Dam53c974.c412 * The am53c974 HBA has a design flaw of generating in pci_esp_probe_one()
/openbmc/qemu/ui/
H A Dinput.c332 * when 'alt+print' was pressed. This flaw is now fixed and the in qemu_input_event_send()
/openbmc/linux/drivers/ata/
H A Dpata_it821x.c59 * flaw that it has a single set of PIO/MWDMA timings per channel so
/openbmc/linux/drivers/char/tpm/
H A Dtpm_tis_core.c724 * Early probing for iTPM with STS_DATA_EXPECT flaw.
/openbmc/linux/drivers/usb/class/
H A Dusblp.c1055 * have this flaw (HP 810, 880, 895, etc.), or needing an init string
/openbmc/qemu/qapi/
H A Dui.json945 # 'alt+print' was pressed. This flaw is now fixed and the 'sysrq' key
/openbmc/linux/Documentation/admin-guide/
H A Dras.rst94 Just detecting a hardware flaw is usually not enough, as the system needs
/openbmc/linux/Documentation/scsi/
H A Dsym53c8xx_2.rst466 if only one has a flaw for some SCSI feature, you can disable the
/openbmc/linux/kernel/
H A Dseccomp.c461 /* Assume default seccomp processes want spec flaw mitigation. */ in seccomp_assign_mode()
/openbmc/linux/drivers/net/wireless/atmel/
H A Dat76c50x-usb.c1181 likely to compensate a flaw in the AT76C503A USB part ... */

12